Subj : Re: Blam BBS List question
To   : Alpha
From : The Godfather
Date : Thu May 28 2020 00:53:29

 Al> You may be correct here. Today I wrote a script to convert the fsxnet
 Al> nodelist into a web-usable format (JSON) and I had to do a lot of
 Al> fiddling to hide ZONE, HOST, PVT, DOWN, etc. read the flags and
 Al> translate them, but I *was* able to do it. 
 Al> 
 Al> http://167.172.194.72:1234/fsxnet

The only challenge I've seen with any script that pulls from the nodelist to
a BBSlist is that the telnet ports are not usually listed within a nodelist. 
So ... this takes, what, 50% of the BBS's and makes them not able to be
connected to via the displayed list if only the URl is listed to the user. 
With my limited knowledge, I can't imagine an easy way to do this for the Net
Admin, or the person writing the script.  Wouldn't either the admin have to
go in and add flags and port numbers to each node and/or wouldn't the script
have to search a range of ports for the listed URL to discover the correct
one, and then populate said telnet port into the BBS list?  I may be wrong
but from a "fresh set of newbie eyes," to me a nodelist used as a BBS list to
display to users is currently useless to 50% of the BBS's who have abandoned
port 23 and/or a lot of work for the network admin (unless a script can
acheive this goal automatically with simply a URL or IP address...)

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
 * Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

.