it should also be pointed out that the FTN MSGID standard limits MSGIDs to only 3 years before the serial numbers may be repeated... dupe detection will eliminate many...
Then disable dupe detection or limit each segment to 3 years. It is not necessary to have 1 monolith message base containing data for all years at once. The message base can be broken up into static sections. Or somebody c
not to mention that it is about 30 years too late getting started...
It is not too late. Try telling Jason Scott that it is too late.
yes, it is too late because the messages are simply gone... deleted
during system maint as they were purged out due to the operators'
message retention settings... we won't even mention all the ones that
were lost when a message base overflowed and corrupted itself requiring deletion of the message base data files...
Nevermind that lazy bullshit that is MSGID... its really just for
reply linking which most messages from the 80's and 90's didn't have.
The only "challenge" is deciding on a storage method for containing
large amounts of messages.
Nothing is ever purged here. I have message bases going back to....
early 2000's I think? Would love to help out or help track down older stuff.
Nick
Nevermind that lazy bullshit that is MSGID... its really just for reply linking which most messages from the 80's and 90's didn't have. The only "challenge" is deciding on a storage method for containing large amounts of messages.
Any modern database will handle it.
You can setup multiple D'Bridge nodes to process gigabytes of mail 24/7. Ha a web status page or echo announcing statistics (eg. volume, messages processed, number of [new] contributors, echo size etc).
Someone would have to write a tosser for the database.
My initial thoughts were for a downloadable database like Wikipedia that SysOps can use as a datasource for whatever they want. They can build servi around it, write more import/export scripts, use it to catchup missing mail performance and stress test tools etc. The fun lies in the system design an implementation. Maybe it can run on block chain.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 17:35:52 |
Calls: | 243 |
Files: | 5,529 |
Messages: | 224,197 |