Hello Warpslide & deon!
Id happily run as a hub for it - and can relinquish that (if required when Frank returns.
Awesome, thanks Deon.
I might make an effort to reach out to those on the SciNet nodelist and see if they'd be interested in connecting up to you as well. I'd direct
If/when this is realized, I'd be interested in joining the alternative feed (hub)!
The main hub (77:1/100) appears to be down since July 27, as you have already pointed out. Although a couple of days isn't really that much time -- maybe we should wait at least a week or two? Of course checking for interest in the mean time is a good idea, should the outage persist!
Deon, if/when this is realized, please feel free to add me to all message & file echo areas and assign a random password (same password for session, PKT, Areafix and Filefix would be just fine) and send it to me somehow (e.g. crashmail to Zip at 77:2/107@scinet) together with the connection details, and I'll start polling you. Thanks in advance!
Speaking of this, if we do change the mail flow, should we all queue a copy of all our new messages to 77:1/100 as well, so that if/when Frank's system is up again (and if/when he returns) he will be able to catch up? As messages don't take much space.
Or should we just export everything new to the new hub only, and then see if/when his system comes up again, and if/when we hear from him, and take it from there (e.g. revert and discuss the future mail flow with him)? Of course, performing "parallel exports" would result in getting all [others'] new messages back as dupes once the main hub comes up again...
Just thinking aloud.
Best regards
Zip (77:2/107@scinet)
--- Mystic BBS v1.12 A47 2021/07/28 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)