I've been thinking about if this would be useful for BBSes.
Thoughts?
Re: MSSP
By: dragon to DOVE-Net.Synchronet_Discussion on Tue Mar 09 2021 02:37 pm
> I've been thinking about if this would be useful for BBSes.
>
> Thoughts?
Looks interesting, but pretty MUD-specific.
Also... Telnet option? Ugh. That's a terrible idea for a new protocol. :-(
I understand it has the benefit of using the same TCP port/stream already in use for the MUD, but then that precludes use of other/better terminal protocols (e.g. SSH).
If you want stats from Synchronet BBS, I recommend using finger. The Synchronet fingerservice has a lot of (potentially interesting) stats available for anyone that wishes to query and it's very easy to extend (unlike the MSSP protocol).
I'm not against using finger, I just am trying to think beyond
Synchronet on this.
Re: Re: MSSP
By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
> I'm not against using finger, I just am trying to think beyond
> Synchronet on this.
Finger is not a Synchronet-only technology. :-)
Re: Re: MSSP
By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
> I'm not against using finger, I just am trying to think beyond
> Synchronet on this.
Finger is not a Synchronet-only technology. :-)
On 3/10/2021 4:29 AM, Digital Man wrote:
Re: Re: MSSP
By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
> I'm not against using finger, I just am trying to think beyond
> Synchronet on this.
Finger is not a Synchronet-only technology. :-)
I'm aware, but do other BBS packages have a finger server already integrated?
On 3/10/2021 4:29 AM, Digital Man wrote:
Re: Re: MSSP
By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
> I'm not against using finger, I just am trying to think beyond
> Synchronet on this.
Finger is not a Synchronet-only technology. :-)
I put together a little test version of what I had in mind.
Telnet to bbs2.ipingthereforeiam.com:2323, enter "info" as the username.
Re: Re: MSSP
By: dragon to Digital Man on Wed Mar 10 2021 03:03 pm
> On 3/10/2021 4:29 AM, Digital Man wrote:
> > Re: Re: MSSP
> > By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
>
> > > I'm not against using finger, I just am trying to think beyond
> > > Synchronet on this.
>
> > Finger is not a Synchronet-only technology. :-)
>
> I put together a little test version of what I had in mind.
>
> Telnet to bbs2.ipingthereforeiam.com:2323, enter "info" as the username.
Yeah, that works. Format looks .ini-ish (except for the spaces in the key names, e.g. "MINIMUM AGE=13"), so that should be univerally easy to parse. I'm not sure about all the systems that use login matrices and how difficult querying such systems for that "info" in an authomated fashion via that method might be. Simply connecting and sending "info" is likely to not work on a large percentage of systems (e.g. pause prompts, lightbar menus).
Just an FYI, your login diplay file doesn't work right on > 80 column terminals. Might want to check that out. :-)
On 3/10/2021 9:58 PM, Digital Man wrote:
Re: Re: MSSP
By: dragon to Digital Man on Wed Mar 10 2021 03:03 pm
> On 3/10/2021 4:29 AM, Digital Man wrote:
> > Re: Re: MSSP
> > By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
>
> > > I'm not against using finger, I just am trying to think beyond
> > > Synchronet on this.
>
> > Finger is not a Synchronet-only technology. :-)
>
> I put together a little test version of what I had in mind.
>
> Telnet to bbs2.ipingthereforeiam.com:2323, enter "info" as the username.
Yeah, that works. Format looks .ini-ish (except for the spaces in the key names, e.g. "MINIMUM AGE=13"), so that should be univerally easy to parse. I'm not sure about all the systems that use login matrices and how difficult querying such systems for that "info" in an authomated fashion via that method might be. Simply connecting and sending "info" is likely to not work on a large percentage of systems (e.g. pause prompts, lightbar menus).
The spaces in field names can easily go. The output could be XML even.
Actually, from my studies, the majority of Synchronet systems have a
stock login, but you're right, dealing with matrices and other preambles could be a problem.
That's kind of why I contacted you to see if this was something feasible
to build in to the server software as an option.
I don't even know yet if this is something a significant number of
sysops would be interested in having.
I put together a little test version of what I had in mind.
Telnet to bbs2.ipingthereforeiam.com:2323, enter "info" as the username.
Re: Re: MSSP
By: dragon to Digital Man on Thu Mar 11 2021 11:34 am
> On 3/10/2021 9:58 PM, Digital Man wrote:
> > Re: Re: MSSP
> > By: dragon to Digital Man on Wed Mar 10 2021 03:03 pm
>
> > > On 3/10/2021 4:29 AM, Digital Man wrote:
> > > > Re: Re: MSSP
> > > > By: dragon to Digital Man on Tue Mar 09 2021 11:57 pm
> > >
> > > > > I'm not against using finger, I just am trying to think beyond
> > > > > Synchronet on this.
> > >
> > > > Finger is not a Synchronet-only technology. :-)
> > >
> > > I put together a little test version of what I had in mind.
> > >
> > > Telnet to bbs2.ipingthereforeiam.com:2323, enter "info" as the
> > username.
>
> > Yeah, that works. Format looks .ini-ish (except for the spaces in the key
> > names, e.g. "MINIMUM AGE=13"), so that should be univerally easy to parse.
> > I'm not sure about all the systems that use login matrices and how
> > difficult querying such systems for that "info" in an authomated fashion
> > via that method might be. Simply connecting and sending "info" is likely
> > to not work on a large percentage of systems (e.g. pause prompts, lightbar
> > menus).
>
>
> The spaces in field names can easily go. The output could be XML even.
I would recommend ini, json, or maybe yaml (in that order) instead of XML.
> Actually, from my studies, the majority of Synchronet systems have a
> stock login, but you're right, dealing with matrices and other preambles
> could be a problem.
>
> That's kind of why I contacted you to see if this was something feasible
> to build in to the server software as an option.
There's already something very much like this in the Synchronet fingerservice:
finger ?stats.json@vert.synchro.net
Additional queries like that are trivial to add (no code change to the server).
Building it into the Telnet protocol is certainly possible, but like I said, limits use to only over Telnet.
> I don't even know yet if this is something a significant number of
> sysops would be interested in having.
Not sure on that front either. Some BBSes might consider those kinds of stats (e.g. number of users) as private data.
BTW, I enabled the finger service on my Synchronet, but I keep getting "Connection refused".
> That's kind of why I contacted you to see if this was something feasible
> to build in to the server software as an option.
There's already something very much like this in the Synchronet fingerservice:
finger ?stats.json@vert.synchro.net
Additional queries like that are trivial to add (no code change to the server).
Building it into the Telnet protocol is certainly possible, but like I said, limits use to only over Telnet.
> I don't even know yet if this is something a significant number of
> sysops would be interested in having.
Not sure on that front either. Some BBSes might consider those kinds of stats (e.g. number of users) as private data.
Actually, all of those detail stats I only put in because it was easy in Synchronet.
What I would be most interested in would be:
BBSNAME
IPADDRESS
TELNETPORT
RLOGONPORT
SSHPORT
CONTACTEMAIL
WEBPAGE
CITY
STATE
COUNTRY
ADULT
MINAGE
PAY
FTNADDRESS
DESCRIPTION
I'm ready to let this topic rest for a while and wait to see if anyone
else chimes in with any interest.
BTW, I enabled the finger service on my Synchronet, but I keep getting "Connection refused".
BTW, I enabled the finger service on my Synchronet, but I keep getting "Connection refused".
The finger issue was that the service apparently can't reload if an NNTP session is active.
On 3/10/2021 1:03 PM, dragon wrote:
I put together a little test version of what I had in mind.
Telnet to bbs2.ipingthereforeiam.com:2323, enter "info" as the username.
Is this an existing standard? It feels like using a standard format,
JSON, YAML, TOML, INI etc would be best... and probably a fixed route definition over HTTP(S).
Sysop: | Rempala |
---|---|
Location: | Richlands, NC |
Users: | 106 |
Nodes: | 10 (0 / 10) |
Uptime: | 40:46:59 |
Calls: | 205 |
Files: | 6 |
Messages: | 111,123 |