Subj : Re: Nodelist Development
To   : Spectre
From : Avon
Date : Sat May 30 2020 16:31:48

On 30 May 2020 at 01:28p, Spectre pondered and said...
 
 Sp> 1/ Incorporate Webring information into the nodelist.
 Sp>        - Website URL
 Sp>        - Telnet Port
 Sp>        - SSH port it required.
 Sp>        - System name as you'd like it formatted in the webring list.

I think to date my use of ITN flag to denote a BBS running on a non-standard
telnet port has been incorrect as the flag I now think was intended from a
mailer point of view (as the historical use is nodelist as a tool for
mailers) to show it a system accepting mail via Telnet was not on port 23 but
port XYZ..

I'm not sure if use of ITN such I have been doing is the best way forward.

Likewise the IBN does the same for BinkP mailers not running on the default
port of 24554 and I use that  IBN flag quite a bit for nodes and HUBs doing
the same.

All of which leads me to think if we were to add flags to a fsxNet nodelist
to help with a webring project or a mod like gy-blam perhaps we should
probably be creating and using some fsxNet created user flags instead?

http://ftsc.org/docs/fts-5001.006 refers to the U flag and a limit of 32
chars per usage but U could be used multiple times in an entry. How I am not
sure as how does anything discern one flag from another if the flag is the
same name??

I see Frank uses U to showcase SciNet nodes custom domain names but if he was
to add another user flag then what?

[snip]

INA:bbs.darkrealms.ca,IBN,U,darkrealms.scinet-ftn.org
INA:therockbbs.net,IBN,ITN:10023,U,therock.scinet-ftn.org

[snip]

So I'm wondering

1. is the nodelist the best place to 'fix' the things were trying to sort?

2. should we be shipping in the infopack or have online some where (or both)
a dynamic txt file that can be used by mods etc. to pull the data needed from
each node in the network for the needs of the mod?

3. If we agree things like 

- non standard telnet ports
- ssh port
- tor port/address info
- what else needs to be added to this list?

....should be in the nodelist should be not be creating our own standardised
user flags instead and then mods would use them?

One downside with the last idea is mods are only going to be able to use the
fsxNet nodelist or whatever txt file that contain the flags we're after for
whatever service they deliver. That's not a deal breaker to me but something
to be aware of.

Perhaps something like fsxNet F flags in the nodelist?

FTEL - telnet port
FSSH - ssh port
FTOR - tor address


I'll stop there :)

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.