What's the socially acceptable maximum message length for BinkP/D FDN mailers? Not lines, but bytes.
That's going to be subjective. Technically speaking,
binkd mailers can transmit files of almost any size,
though I suspect a lot of software would have trouble
with files over about 2GiB. But socially speaking?
Most packets I see on my system are under a kilobyte;
I figure 2K to 4K would be reasonable.
Gents,
What's the socially acceptable maximum message length for BinkP/D FDN mailers? Not lines, but bytes.
Mystic allows 1000 and then will cut it although those limits are less needed these days. But back in the day someone could post a 500k
document in a message and it gets sent across a network costing everyone
a couple of dollars each just to push the message, so you can see why limits were needed.
So assuming Mystic, 80 chars/line * 1000 lines of Base64 encoded
payloads is around < 80k of payload data. So a Mb of payload would span around ~13 messages running to the brim.
I think my idea is too risky to run over embedded payloads. I'll conjure up something else. I don't even want to think of payloading 1Mb at 100 lines.
Maybe a better solution could be to run a service that allows whatever script or function you want to enable on end point BBS systems to
connect to the server and get the data they need. You could have a data file on a FTP or HTTP server that BBSes can pull down through a script
or something instead of sending it through an echomail base.
Yeah I'm trying to figure out a way to pass a few megs of data via messages, not hatched files since we don't have hatch access to most
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,049 |
Nodes: | 15 (1 / 14) |
Uptime: | 186:46:08 |
Calls: | 233,564 |
Calls today: | 5 |
Files: | 60,153 |
D/L today: |
839 files (186M bytes) |
Messages: | 292,322 |
Posted today: | 1 |