• Zone 1 Host 114

    From Andy Gorman@1:229/426.52 to All on Friday, October 08, 2021 14:59:30
    Hi everyone - does anyone know if the RC for 1:114(TJ Barlow) is still around by chance?

    You haven't defined an auto-signature yet. Or have I?

    --- Mystic BBS v1.12 A47 2021/05/03 (Windows/64)
    * Origin: The Pot O'Gold - bbs.thepotogold.net:4888 (1:229/426.52)
  • From Nick Andre@1:229/426 to Andy Gorman on Saturday, October 09, 2021 01:21:38
    On 08 Oct 21 14:59:30, Andy Gorman said the following to All:

    Hi everyone - does anyone know if the RC for 1:114(TJ Barlow) is still arou by chance?

    TJ answers my emails... slowly.

    Nick
    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Wilfred van Velzen@2:280/464 to Andy Gorman on Saturday, October 09, 2021 10:46:42
    Hi Andy,

    On 2021-10-08 14:59:30, you wrote to All:

    Hi everyone - does anyone know if the RC for 1:114(TJ Barlow) is still around by chance?

    Have you tried all his aka's?

    1 Region,15,Mountain_States,AZ_CO_NM_UT_WY,Tj_Barlow,-Unpublished-,9600,CM,XX,IBN,ITN,INA:region15.net,IBN:24555
    2 ,1,Region15_Echomail_Coordinator,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XX,IBN,ITN,INA:region15.net,IBN:24555
    3 ,2,Region_15_HQ_Backup,Colorado_Springs_CO,Tj_Barlow,-Unpublished-,9600,ICM,IBN,IFT,IFC,ITN:60177,INA:bk.region15.net
    4 ,3,Region_15_News_Hub,Colorado_Springs_CO,Tj_Barlow,-Unpublished-,9600,ICM,IBN,IFT,IFC,ITN:60177,INA:region15news.net
    5 Host,114,NC_Net_114_Arizona,Colorado_Springs_Co,Tj_Barlow,-Unpublished-,9600,CM,XX,INA:cscnet1.net,IBN,IFT,ITN:60177
    6 Host,128,Pikes_Peak_Net_NC,Colorado_Springs_CO,Terry_Barlow,1-719-550-9599,9600,CM,XA,XX,H16,V32b,V42b,V34,V32t,X2C,INA:cscnet1.net,IBN
    7 ,1,Pikes_Peak_Net_NEC,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,INA:cscnet1.net,IBN
    8 ,187,Colorado_Springs_Central_Net,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,INA:cscnet1.net,IBN
    9 ,253,StarBase_Alpha,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,INA:barlows1.net,IBN
    10 Down,254,Old_School_Colorado_Springs_Central_Net,Colorado_Springs_CO,Terry_Barlow,1-719-550-9599,9600,CM,XA,V32b,V42b,INA:oldschool.cscnet1.net,IBN
    11 Host,305,Southern_New_Mexico,Las_Cruces_NM,Tj_Barlow,-Unpublished-,9600,CM,INA:region15.net,IBN
    12 Host,307,Pueblo_CO_NC,Pueblo_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,XX,H16,V32b,V42b,V34,V32t,X2C,INA:region15.net,IBN
    13 ,1,Region_15_HQ,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,V32b,V42b,INA:region15.net,IBN
    14 Host,310,Cheyenne_WY,Cheyenne_WY,Terry_Barlow,-Unpublished-,9600,CM,XA,XX,H16,V32b,V42b,V34,V32t,X2C,INA:region15.net,IBN
    15 ,1,Region_15_HQ,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,V32b,V42b,INA:region15.net,IBN
    16 Host,311,NC_Net_311,Magna_UT,Terry_Barlow,-Unpublished-,9600,CM,XX,INA:cscnet1.net,IBN,ITN
    17 ,1,Colorado_Springs_Central_Net,Colorado_Springs_CO,Tj_Barlow,-Unpublished-,9600,CM,XA,INA:cscnet1.net,IBN
    18 Host,312,NC_Net_312,Provo_UT,Terry_Barlow,-Unpublished-,9600,CM,XA,INA:cscnet1.net,IBN
    19 ,1,Colorado_Springs_Central_Net,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,INA:cscnet1.net,IBN
    20 Host,317,Northern_New_Mexico,Albuquerque_NM,Tj_Barlow,-Unpublished-,9600,CM,INA:region15.net,IBN
    21 ,1,Colorado_Springs_Central_Net,Colorado_Springs_CO,Tj_Barlow,-Unpublished-,9600,CM,XA,INA:cscnet1.net,IBN
    22 Host,3005,Internet_Only_Nodes,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,XX,INA:region15.net,IBN
    23 ,1,StarBase_Discovery,Colorado_Springs_CO,Terry_Barlow,-Unpublished-,9600,CM,XA,INA:sb-discovery.com,IBN

    Maybe the one you tried isn't monitored by him? Or "maybe" it's mostly rubish that is in the nodelist? :-/

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Björn Felten@2:203/2 to Wilfred van Velzen on Saturday, October 09, 2021 14:42:58
    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...


    ..
    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Nick Andre@1:229/426 to BjöRn Felten on Saturday, October 09, 2021 09:49:58
    On 09 Oct 21 14:42:58, Bj*Rn Felten said the following to Wilfred Van Velzen:

    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 some in Z2 need a little less "relish" on their Nothing Burger.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Wilfred van Velzen@2:280/464 to Bj”rn Felten on Saturday, October 09, 2021 18:44:20
    Hi Bj”rn,

    On 2021-10-09 14:42:58, you wrote to me:

    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...

    And regarding the segment of this RC, if you check all his AKA's you will find most will either not be connectable, or respond with the wrong AKA. This has been the case for many years.
    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. ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Björn Felten@2:203/2 to Wilfred van Velzen on Saturday, October 09, 2021 22:33:01
    They seem to have a none interference policy regarding "lower" segments.

    Maybe it's an attempt to mimic the FidoWeb? After all, it's originally from Z2, and we cannot have that, can we? 8-)

    They accept anything the "lower" *C sends in, even if has the most obvious mistakes, and nonsense...

    Too little Kees!

    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. ;-)

    Considering how much action, like the above mentioned, that takes place there, I doubt it would be of any interest... ;-)




    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Nick Andre@1:229/426 to Wilfred Van Velzen on Saturday, October 09, 2021 16:03:30
    On 09 Oct 21 18:44:20, Wilfred Van Velzen said the following to Bj*Rn Felten:

    They seem to have a none interference policy regarding "lower" segments. Th accept anything the "lower" *C sends in, even if has the most obvious mistakes, and nonsense...

    Thats an interesting observation coming from a Dutch wuss who kissed my ass
    to have a feed here... which I happily provided no-questions-asked. I'm going to assume the Z2 segment is therefore perfect and every stinken' node can be reached at all times? Or do you have the Happy Belgian modifying segments?

    Imagine the suspenders flapping in the wind if I did that... you would have react more excited than you do when a new node flies that stupid Ping flag.

    A Nothing Burger goes down good with a nice tall refreshing glass of STFU.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Kurt Weiske@1:218/700 to Bj÷rn Felten on Saturday, October 09, 2021 07:08:00
    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...

    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.

    Or, do you really think that a coordinator in this day and age is trying to wear more hats?




    ... How did you find this place?
    --- MultiMail/DOS v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
  • From Björn Felten@2:203/2 to Kurt Weiske on Tuesday, October 12, 2021 20:20:49
    Or, do you really think that a coordinator in this day and age is trying to
    wear more hats?

    Nah! Only kids worry about Mickey Mouse hats.



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Wilfred van Velzen@2:280/464 to Kurt Weiske on Wednesday, October 13, 2021 09:53:11


    Hi Kurt,

    On 2021-10-09 07:08:00, you wrote to Björn Felten:

    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.

    In the case of the RC15, it's stuffing for a large part. For instance all the ,1, nodes serve no purpose, and could just be removed.

    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.

    What value has it to keep the auto-pilot nodes in a net? They probably will just disappear without notice in the future. And I hope there will be somebody arround to notice this and remove them from the nodelist (after a little 'Down' period).

    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.

    Well, good for you, you did a nice job!

    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

    So none of the Hosts exist! The only Net in this region that has someone else listed as Host, only has a phonenumber to connect to (I can't test that). My conclusion, this Region only exists in the fantasy of mister Barlow, and could be safely removed. Mister Barlow can then apply for a nodenumber somewhere else.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Kurt Weiske on Wednesday, October 13, 2021 11:15:02
    Hi Kurt,

    On 2021-10-13 09:53:11, I wrote to you:

    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

    Updated results after a while:
    (Maybe Mystic/binkp has a problem handling multiple connects at the same time? Or it's some kind of firewall issue)

    1:114/0 cscnet1.net Remote has no needed AKA
    1:128/0 cscnet1.net CONNECT/BND
    1:128/1 cscnet1.net CONNECT/BND
    1:128/187 cscnet1.net CONNECT/BND
    1:311/0 cscnet1.net Remote has no needed AKA
    1:311/1 cscnet1.net Remote has no needed AKA
    1:312/0 cscnet1.net Remote has no needed AKA
    1:312/1 cscnet1.net Remote has no needed AKA
    1:317/1 cscnet1.net Remote has no needed AKA

    So there actually exists 1 (of 9) Hosts in the Region... :-/

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)