Hi everyone - does anyone know if the RC for 1:114(TJ Barlow) is still arou by chance?
Hi everyone - does anyone know if the RC for 1:114(TJ Barlow) is still around by chance?
Maybe the one you tried isn't monitored by him? Or "maybe" it's mostly rubish that is in the nodelist? :-/
Maybe the one you tried isn't monitored by him? Or "maybe" it's mostl rubish that is in the nodelist? :-/
WOW! That's a lot of nodelist stuffing. Maybe someone responsible for th Z1 segment needs to wake up...
Maybe the one you tried isn't monitored by him? Or "maybe" it's
mostly rubish that is in the nodelist? :-/
WOW! That's a lot of nodelist stuffing. Maybe someone responsible for the Z1 segment needs to wake up...
They seem to have a none interference policy regarding "lower" segments.
They accept anything the "lower" *C sends in, even if has the most obvious mistakes, and nonsense...
But then again, if you want to read Z1C or even Z1REGCON, his bbs's
(that are connectable) are a good place to do that. ;-)
Björn Felten wrote to Wilfred van Velzen <=-
Maybe the one you tried isn't monitored by him? Or "maybe" it's mostly rubish that is in the nodelist? :-/
WOW! That's a lot of nodelist stuffing. Maybe someone responsible
for the Z1 segment needs to wake up...
Or, do you really think that a coordinator in this day and age is trying to
wear more hats?
Maybe the one you tried isn't monitored by him? Or "maybe" it's
mostly rubish that is in the nodelist? :-/
WOW! That's a lot of nodelist stuffing. Maybe someone responsible
for the Z1 segment needs to wake up...
It's not stuffing, it's called attrition.
I had a handful of nets where I was the RC and NC, as a node or two
wanted to hold onto their node numbers when the NC left. There's a tightrope you walk; make too many changes and sysops decide it's
easier to take down nodes running on auto-pilot than make major
changes.
Over the years I've closed down several nets and have my region with
one historical net in use with an active BBS author, nets with sysops
who want to be their own NC, and an IP-only net that's geography independent. I did it one BBS at a time, and handled it with kid
gloves. If I'd set a date and closed down all of the NC-less nets at
once I bet I'd have lost a good portion of my nodes.
Now lets look at the nodelist entries by the RC15. I did a little scripting and polled them all. The results were worse than I
expected:
1:15/0 region15.net:24555 CONNECT/BND
1:15/1 region15.net:24555 CONNECT/BND
1:15/2 bk.region15.net Connection timed out
1:15/3 region15news.net Connection timed out
1:114/0 cscnet1.net connection closed by foreign host
1:128/0 cscnet1.net connection closed by foreign host
1:128/1 cscnet1.net connection closed by foreign host 1:128/187 cscnet1.net connection closed by foreign host 1:128/253 barlows1.net Connection timed out
1:128/254 oldschool.cscnet1.net Remote has no needed AKA (Despite being marked as Down)
1:305/0 region15.net Remote has no needed AKA
1:307/0 region15.net Remote has no needed AKA
1:307/1 region15.net Remote has no needed AKA
1:310/0 region15.net Remote has no needed AKA
1:310/1 region15.net Remote has no needed AKA
1:311/0 cscnet1.net connection closed by foreign host
1:311/1 cscnet1.net connection closed by foreign host
1:312/0 cscnet1.net connection closed by foreign host
1:312/1 cscnet1.net connection closed by foreign host
1:317/0 region15.net Remote has no needed AKA
1:317/1 cscnet1.net connection closed by foreign host 1:3005/0 region15.net Remote has no needed AKA
1:3005/1 sb-discovery.com Connection timed out
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 140:11:59 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,236 |