Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    TUXPOWER    |    Advocacy for the Linux operating system    |    1,237 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 830 of 1,237    |
|    Nicholas Boel to Maurice Kinal    |
|    Re: this split is limited to -b 2000m    |
|    17 Nov 24 08:52:25    |
      TZUTC: -0600       MSGID: 174.tuxpower@1:154/700 2b9f39d7       REPLY: 1:153/7001.2989 67398f68       PID: Synchronet 3.20a-Linux master/9bf86ab10 Nov 16 202 GCC 14.2.1       TID: SBBSecho 3.22-Linux master/9bf86ab10 Nov 16 2024 18:25 GCC 14.2.1       BBSID: PHARCYDE       CHRS: ASCII 1       NOTE: slrn/pre1.0.4-9 (Linux)       Hello Maurice,              On Sun, Nov 17 2024 00:38:32 -0600, you wrote:              > How deep do you wish me to delve into it? At the moment it is part and       > parcel of a bash script that does it all, reply-wise. I forget the last time       > I did any serious work on it and it will take me some time to isolate just       > the quoting aspect. It is doable though since it started out as an isolated       > bit of code and I might even have a backup of that initial work which if true       > will speed up the process.              Probably just the quoting part. I'm currently using slrn (a console based NNTP       newsreader) that handles the messages themselves. When I reply/follow-up to a       message it craps the message out to a text file which I pick up in vim or       nano. Obviously, standard newsreader quoting etiquette is applied with no       fancy FTN stuff going on.              > NB> That's about to change, though.              > I noticed. What version are you deploying?              > |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca