Sean Dennis wrote to Alan Ianson:

SD> If someone's posting 400K messages, they ought to be slapped.

I dunno how big he is.. :)

SD> Any sysop would realize that not everyone's systems can handle messages 
SD> that ¨big and put them into 64K chunks (possibly still, 16K).  But to be 
SD> honest, who ¨really needs that kind of statistical data broadcast?  I can 
SD> see a major hub ¨generating statistics locally, but really now, 400K? :)

Yep, I exported one to a file last night to see, 451Kb.. it's a bigun. :)
It contains a list of every message area that hub carries (many nets)
that lists how many messages were sent & recieved in those areas. I read
the area from time to time just to see what areas are getting traffic
and be sure I am connected.. :)

It's a tough read for sure but lots of good info if FTN traffic is what
your looking for.

SD> I do believe that you aren't going to see any tosser go over 64K, period.  
SD> I ¨read the docs and FE does cut the packets as does Squish.  I can't 
SD> speak for ¨any other tosser, but those two do truncate the message.

Squish skips a message if it's to large, so your links don't get the
message at all and it's not in your own message base. FE tries to toss
the message but when the buffer runs out.. that's the end of that.

As far as FTSC standards go, message size is unbounded (from what I
understand). Still, I believe you are right about message size. A
large message should be split so all interested parties get it. It'll
still be a big message, just in a few pieces.

 Ttyl :-),
         Al

... Dew knot trussed yore spell chequer two fined awl mistakes!

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)