🚀 go-pugleaf

It seems to me that most BBSs that I hook into allow 1hr connect time.
However, these BBSs are so busy that it is virtually impossible to get
on except between 3:00-5:00AM weekdays and 3:00-9:00AM weekends (EST).
Obviously the demand for file transmission has exceeded resource capacity.
Hence an alternative is desperately needed.  The net is a great alternative
in many ways.  I think it should be utilized immediately for this purpose.
Realizing, however, that there are valid concerns regarding too much
software being put on the net I think that certain restrictions should
be imposed on source/binary transmission.  Exactly what the optimal formula
is I don't know but it probably should involve a combination of file length
and number of transmissions per week.  I would be very happy if everyone
could agree on such a formula because, in my mind, the result would be a 
much more useful net.  While I am here let me propose a formula for binaries:
Let U(P) denote the number of storage units used by program P.  Let S(P)
be the size of a file in kbytes.  Define U(P) as

                       U(P)=S(P) DIV 8

I propose that the total numbers of storage units transmitted over the net
per week be less than 8.  Net users would be asked not to transmit any more
units of data until the number of units transmitted over the previous two
week period fell below 16.  I am not making any great claims for this
proposal...I am just throwing it out for purposes of generating discussion.

By the way - don't ask me for any BBS numbers...if any more people find out
about these numbers I will not be able to get on even saturday morning at
5:00AM (EST).