TZUTC: -0700
MSGID: 11169.bbs_carn@1:103/705 28977d25
REPLY: 11168.bbs_carn@1:103/705 2894bee6
PID: Synchronet 3.20a-Linux master/fcf4a0012 Apr  4 2023 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/f4dcbf61d Apr  5 2023 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: ASCII 1
NOTE: FSEditor.js v1.104
  Re: BBS Software Timeout Values
  By: Rob Swindell to Dennis Scott on Thu Apr 06 2023 05:01 pm

 > Current versions of Synchronet support up to 250 nodes. Realistically,
 > nobody configures anywhere near that many nodes mainly because configuring
 > door games to support dozens of nodes (for many multinode doors, anyway), is
 > a big hassle. It's much easier to just enforce a maximum duration of user
 > inactivity and keep the number of configured nodes to some a number you'd
 > reasonably expect to need for *active* user connections.

Is it realistic to have the BBS software dynamically open and close nodes as
necessary, similiar to the way that Apache does? If so, a Sysop could assign
say 5 nodes or so for doors and the rest of the nodes be dynamic if necessary.

What if there was a way for each Sysop to have an income from their BBS? Maybe
not getting rich but paying for their equipment and bandwidth, etc. I think
there is a way to do it and still keep the BBS system that's been around for
decades.

Cheers,
Dennis
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 1/123 15/0 18/200 90/1 103/705 105/81 106/201 123/131 124/5016
SEEN-BY: 129/305 153/757 7715 154/10 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 111 112 113 206 275 307 317 400 424 426 428 452 470
SEEN-BY: 229/550 664 700 240/1120 5832 266/512 280/464 5003 282/1038
SEEN-BY: 292/8125 301/1 317/3 320/219 322/757 341/66 234 342/200 396/45
SEEN-BY: 460/58 633/267 280 281 412 418 509 712/848
PATH: 103/705 280/464 633/280 229/426