Re: BBS Software Timeout Values
  By: Dennis Scott to Rob Swindell on Sat Apr 08 2023 06:57 pm

 >   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?

Apache web server? It doesn't have the concept of "nodes" or "door games".

 > If so, a Sysop could assign
 > say 5 nodes or so for doors and the rest of the nodes be dynamic if
 > necessary.

Oh, I suppose anything's possible. But it's most mult-user BBSes are designed in a way that when a user connects, they're assigned an "open node" and have exclusive use of that node until they disconnect/log-off and at that time the node is "closed".

 > 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.

You mean if something like paypal existed? It does. And sysops could require payment for access if they wanted to. I don't understand your point.
-- 
                                            digital man (rob)

Synchronet "Real Fact" #13:
Synchronet was the first BBS software to ship with internal QWK networking
Norco, CA WX: 61.9øF, 72.0% humidity, 3 mph SSE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux