I just came on to the tail of this (and also discovered this is a FSX_NET!). Can someone explain what the rationale is for changing nodelists, or even really caring about them much?

I started a nodelist parser a year back or so, but then stopped becuase it just












































































































didn't seem worth it. The format is quite wonky at this point due to years of changes (which is perhaps why this discussion is going on) but even if it were not... really, what would I use it for? In the modern era we're connected up via a minimal set of addresses which I can just read and punch in. A "BBS list"












































































































is an entirely different subject IMO.

Am I missing something here?



--

NuSkooler
Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic

--- ENiGMA 1/2 v0.0.11-beta (linux; x64; 12.13.1)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

NuSkooler wrote (2020-05-30):

I just came on to the tail of this (and also discovered this is a FSX_NET!). Can someone explain what the rationale is for changing nodelists, or even really caring about them much?

[...] A "BBS list" is an entirely different subject IMO.

Am I missing something here?

This was my first thought too: Why? ;)

We should invent some NLDoc format so people could put endless lines of info below their node line as comments - maybe even Base64-encoded pictures of themself. "The sysop, eating Pizza while compiling qico."

---
* Origin: (21:3/102)

On 30 May 2020 at 11:18a, NuSkooler pondered and said...

I just came on to the tail of this (and also discovered this is a FSX_NET!). Can someone explain what the rationale is for changing

:) Hi!

FSX_NET!). Can someone explain what the rationale is for changing nodelists, or even really caring about them much?

There's a couple of ideas kicking around for a improved webring and updated
mod based on one Gryphon created a few years back.

Changes to the nodelist adding extra fields are being mooted as is a new document that could perhaps better serve the needs of the above (and perhaps other yet to be thought of ideas) in lieu of using the nodelist.

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

Today I've worked on the backend system that generates the nodelist for
fsxNet. The nodelist is now built based on segments sent in from NETs vs
being based off one master file I was solely maintaining for all NETs.

While this approach is nothing new in Fidonet it's new for fsxNet and is
well overdue as the network has grown and other able and willing folks have kindly helped by running additional NETs/HUBs over time.

For starters we have NETs 3 and 4 sending in segments and I am continuing to generate NET 1,2 and 5. My plan is to work with Solaris and Zazz to get them
up and running as segment contributors for their respective NETs if they wish to do so.

All things being equal the average node should not see any difference in what they get but from an admin point of view it means NET admins can ensure they take responsibility for their segments in the nodelist and know that what
they submit will be incorporated in the final combined nodelist.

My thanks to Deon and Dan for their help and support with this change :)

Best, Paul

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

Been working away on nodelists again today, I think most of the kinks for the changes made are largely ironed out now. Will look to next week to see how
the next automated run on Friday morning works out.

Next up I'm working on getting past stats reports for BinkP and echomail traffic working again and posted to the file and stats echos.

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