• FidoNews 36:43 [00/07]: The Front Page

    From FidoNews Robot@2:2/2 to All on Mon Oct 28 00:52:03 2019
    The F I D O N E W S Volume 36, Number 43 28 Oct 2019 +--------------------------+-----------------------------------------+
    | |The newsletter of the | | |
    | | FidoNet community. | | Netmail attach to (POTS): |
    | | | | Editor @ 2:2/2 (+46-31-960447) |
    | | ____________| | |
    | | / __ | Netmail attach to (BinkP): |
    | | / / \ | Editor @ 2:203/0 |
    | | WOOF! ( /|oo \ | |
    | \_______\(_| /_) | Email attach to: |
    | _ @/_ \ _ | b @ felten dot se |
    | | | \ \\ | |
    | | (*) | \ ))| |
    | |__U__| / \// | Editor: Bj”rn Felten |
    | ______ _//|| _\ / | |
    | / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
    | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


    Table of Contents
    1. GENERAL ARTICLES ......................................... 1
    Why I resigned as FTSC administrator ..................... 1
    2. LIST OF FIDONET IPV6 NODES ............................... 3
    List of IPv6 nodes ....................................... 3
    3. JAMNNTPD SERVERS LIST .................................... 6
    The Johan Billing JamNNTPd project ....................... 6
    4. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 7
    5. SPECIAL INTEREST ......................................... 14
    Statistics from the Fidoweb .............................. 14
    Nodelist Stats ........................................... 15
    6. FIDONEWS INFORMATION ..................................... 17
    How to Submit an Article ................................. 17
    Credits, Legal Infomation, Availability .................. 19

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Oct 28 00:52:03 2019
    =================================================================
    GENERAL ARTICLES =================================================================

    Why I resigned as FTSC administrator
    By Michiel van der Vlist (2:280/5555) (ex 2:2/20)

    On 1 November 2018, now almost a year ago, I resigned as FTSC
    administrator. Why?

    Short answer: The fun was gone.

    Long answer:

    The FTSC has always been running behind the facts in that it docu-
    ments current practise created by others instead of creating it
    herself. That was the theory anyway. But at least the situation has
    always been that once something was documented as a standard, it was
    considered binding. Or at least that POV was supported by the powers
    that be. More precise: the FTSC had the support of the *C structure.

    In the autumn of 2017 something happened that dramatically changed
    that position.

    ZC2 in his infinite wisdom decreed that so called ,MOB nodes were
    welcome in Fidonet. They are mobile nodes running HotdogEd or
    AfterShocK. Presently such nodes can not accept incoming calls in
    almost all mobile networks in Z2. Those nodes have the reachability
    of a point. By accepting such nodes as fully fledged nodes, ZC2
    single handedly changed the requirements for Fidonet membership. He
    did that all by himself without consulting any other Fidonet members.

    *1)

    Where it concerned the FTSC is that he also decreed that such nodes
    are to be listed without the Pvt keyword. Like this:

    ,865,Lucas_Visions,Mortsel,Luc_Sienaert,-Unpublished-,300,U,MOB

    As these nodes are listed without any contact information, they are
    private nodes as per FTS-5000.005 par 5.3. So they should be listed
    with the Pvt keyword. The Pvt keyword serves to make software aware
    that it should not attempt to connect directly but route mail through
    the hub or host. This mechanism has been in use almost from the start
    of Fidonet.

    I tried to explain this to the ZC and - mandated by FTA-1001.007 -
    strongly advised him to drop the wicked idea of listing uncontactable
    nodes without the Pvt keyword. It fell on deaf ears. The ZC insisted
    they should be listed without Pvt.

    At the time of the ZC's decree, Belgium (net 292) and The Netherlands
    (net 280) were united in Region 28. I was RC28 (elected). As a side
    note I should add that net 292 is so big that maintaining its
    nodelist segment and routing the mail seems to be such a gigantic task
    that it is too much for the NC292 alone to handle. The help of a Hub
    operator is apparently required. The sysop of Hub 292/80 is Ward
    Dossche. This Hub operator maintains his own section of the nodelist.

    I received a net segment from NC292 with, among other changes, the
    line above. The line was in the segment of Hub 80. I rejected the
    net 292 segment as in violation of FTS-5000. My POV was that these
    nodes do not belong in the nodelist at all but should participate in
    Fidonet as points. As a compromise however, I offered to have them
    listed as Pvt nodes. The offer was rejected and I was told the FTSC
    standards are not binding and I was /ordered/ by the ZC to accept and
    process the net 292 segment as submitted. I refused. A decision based
    on technical grounds as mandated by par. P4 3.8.

    As a result the sysops of net 292 decided they no longer wanted to be
    part of Region 28. Or so I was told by the ZC2. I was not given the
    opportunity to check with the rest of the sysops of net 292. Region
    29 was reinstated and the new RC29 accepted a net 292 segment with
    ,MOB nodes without the Pvt keyword. Problem solved.

    NOT. This was unacceptable to me. Not the splitting of the region as
    such, but the fact that the FTSC standard was set aside just like
    that by the ZC. By decree.

    It killed my motivation. Against my better judgement I waited a year
    in hope that my motivation would return. But it didn't. The damage
    was done and it was permanent. The drive was gone. I was no longer
    motivated to spend time and energy on documenting standards that can
    be nullified just like that by decree of the ZC.

    Fidonet is a hobby. Hobbies are supposed to be fun. For me the fun of documenting standards for Fidonet was gone when I was told by my ZC
    that the documented standards are not binding and when he attempted
    to force me to act in violation of the standards. And when I refused,
    he split up the region in order to get his way. It was not the first
    clash with my ZC but it was the brick that broke the camel's back.
    The damage is permanent and irreversible. The fun was gone, I decided
    I would not waste any more time and energy on the FTSC. Time to move
    on. Hence my resignation as FTSC head honcho.

    Michiel van der Vlist. (2:280/5555) (ex 2:2/20)

    *1) Fidonews 34-37, 11 Sept 2017.


    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Oct 28 00:52:03 2019
    =================================================================
    LIST OF FIDONET IPV6 NODES =================================================================

    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 26 Oct 2019


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f PO4
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula T-6in4 he.net f
    7 2:221/6 Tommi Koivula T-6in4 he.net f
    8 2:5053/54 Denis Mikhlevich Native TTK-Volga
    9 2:5030/257 Vova Uralsky Native PCextreme
    10 1:154/10 Nicholas Bo‰l Native Spectrum f
    11 2:203/0 Bj”rn Felten T-6in4 he.net
    12 2:280/5006 Kees van Eeten Native Xs4All f INO4
    13 3:712/848 Scott Little T-6RD iiNet f IO
    14 2:5020/545 Alexey Vissarionov Native Hetzner f
    15 1:103/17 Stephen Hurd T-6in4 he.net
    16 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    17 2:301/812 Benoit Panizzon Native IMPNET DOWN
    18 2:421/790 Viktor Cizek T-6in4 he.net
    19 2:222/2 Kim Heino Native TeliaSonera
    20 3:633/280 Stephen Walsh Native AusNetServers f
    21 2:463/877 Alex Shuman Native Nline f IO
    22 1:19/10 Matt Bedynek T-6in4 he.net
    23 3:770/1 Paul Hayton T-6in4 he.net
    24 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    25 1:103/1 Stephen Hurd Native Choopa
    26 3:633/281 Stephen Walsh Native Internode
    27 2:310/31 Richard Menedetter Native DE-NETCUP f
    28 3:633/410 Tony Langdon Native IINET
    29 2:5020/329 Oleg Lukashin Native Comfortel f
    30 2:246/1305 Emil Schuster Native TAL.DE
    31 2:2448/4000 Tobias Burchhardt Native DTAG IO
    32 2:331/51 Marco d'Itri Native BOFH-IT
    33 1:154/30 Mike Miller Native LINODE
    34 1:282/1031 Jeff Smith T-6in4 he.net
    35 2:5001/100 Dmitry Protasoff Native Hetzner
    36 2:5059/38 Andrey Mundirov T-6in4 he.net
    37 2:240/5853 Philipp Giebel Native Hetzner
    38 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    39 1:123/10 Wayne Smith T-6in4 he.net
    40 2:5021/46 Dmitry Komissarov Native THEFIRST
    41 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    42 1:135/300 Eric Renfro Native Amazon.com
    43 1:103/13 Stephen Hurd Native Choopa
    44 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    45 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    46 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    47 4:902/26 Fernando Toledo T-6in4 he.net
    48 2:5019/400 Konstantin Kuzov Native LT-LT
    49 2:467/239 Mihail Kapitanov T-6in4 he.net f
    50 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    51 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    52 2:5020/736 Egor Glukhov Native VPSVILLE f
    53 2:280/2000 Michael Trip Native Xs4All
    54 2:230/38 Benny Pedersen Native Linode
    55 2:460/58 Stas Mishchenkov T-6in4 he.net f
    56 1 135/367 Antonio Rivera Native RRSW-V6
    57 2:5020/2123 Anton Samsonov T-6in4 he.net
    58 2:5020/2332 Andrey Ignatov Native ru.rtk
    59 2:5005/49 Victor Sudakov T-6in4 he.net
    60 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    61 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    62 1:153/757 Alan Ianson Native TELUS
    63 2:5057/53 Ivan Kovalenko T-6in4 he.net f
    64 2:5020/921 Andrew Savin Native Starlink
    65 2:5010/352 Dmitriy Smirnov Native EkranTV f
    66 2:292/854 Ward Dossche Native Proximus OO
    67 2:469/122 Sergey Zabolotny Native ARUBA-NET f
    68 2:5053/400 Denis Mikhlevich Native TTK-Volga
    69 1:135/371 Eric Renfro Native Cox Communications
    70 2:250/5 Christian Sacks Native Sky Broadband
    71 2:240/1634 Hugo Andriessen Native M-net
    72 2:421/21 Stepan Gabriel Native NETDATACOMM
    73 2:466/4 Igor Goroun Native HOS-GUN
    74 2:5030/1997 Alexey Fayans T-6in4 he.net
    75 1:14/6 Jeff Smith T-6in4 he.net
    76 1:220/70 Joseph Werle T-6in4 he.net
    77 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    78 2:240/100 Arno Klein Native OVH
    79 2:5020/2038 Dmitry Kanidev Native RU-MGTS INO4
    80 2:2452/502 Ludwig Bernhartzeder Native DTAG
    81 2:423/39 Karel Kral Native WEDOS
    82 2:5080/102 Stas Degteff T6to4 NOVATOR


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls)
    INO4 No IPv4 (Node can not accept incoming IPv4 calls)
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    DOWN This node is temporarely down for both IPv4 and IPv6
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up). If the destination address is a 6to4 tunnel address
    (2002::/16) many OSs default to IPv4 if an IPv4 address is present.

    Submitted on day 300

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Oct 28 00:52:03 2019
    =================================================================
    SPECIAL INTEREST =================================================================

    Last week's statistics from the Fidoweb
    By EchoTime, 2:203/0

    (Some nets may have lost their last
    digit for technical reasons)

    pkt (toss-toss) msg (write-toss)
    nodes mean dev no mean dev no

    154/* 10.4m 13.3m 236 1.0h 3.0h 236
    201/* 0.8m 0.6m 2 11.0h 15.4h 2
    221/* 1.1m 2.2m 293 6.3h 12.8h 293
    280/* 0.9m 2.2m 499 6.2h 5.9h 498
    292/* 4.5m 4.4m 40 2.8h 4.7h 39
    320/* 1.8m 1.2m 311 1.7h 4.0h 310
    423/* 1.3m 0.5m 12 0.0h 0.0h 12
    502/* 1.3m 2.1m 9 7.1h 6.5h 9

    Sigma 2.9m 6.7m 1402 4.2h 7.7h 1399

    -----------------------------------------------------------------
    Nodelist Stats

    Input nodelist nodelist.298
    size 184.5kb
    date 2019-10-25

    The nodelist has 992 nodes in it
    and a total of 1464 non-comment entries

    including 4 zones
    31 regions
    169 hosts
    67 hubs
    admin overhead 271 ( 27.32 %)

    and 115 private nodes
    36 nodes down
    50 nodes on hold
    off line overhead 201 ( 20.26 %)


    Speed summary:

    >9600 = 56 ( 5.65 %)
    9600 = 218 ( 21.98 %)
    (HST = 8 or 3.67 %)
    (CSP = 0 or 0.00 %)
    (PEP = 0 or 0.00 %)
    (MAX = 0 or 0.00 %)
    (HAY = 0 or 0.00 %)
    (V32 = 81 or 37.16 %)
    (V32B = 25 or 11.47 %)
    (V34 = 104 or 47.71 %)
    (V42 = 78 or 35.78 %)
    (V42B = 27 or 12.39 %)
    2400 = 1 ( 0.10 %)
    1200 = 0 ( 0.00 %)
    300 = 717 ( 72.28 %)

    ISDN = 32 ( 3.23 %)

    -----------------------------------------------------
    IP Flags Protocol Number of systems -----------------------------------------------------
    IBN Binkp 755 ( 76.11 %) ----------------------------------
    IFC Raw ifcico 88 ( 8.87 %) ----------------------------------
    IFT FTP 62 ( 6.25 %) ----------------------------------
    ITN Telnet 161 ( 16.23 %) ----------------------------------
    IVM Vmodem 11 ( 1.11 %) ----------------------------------
    IP Other 5 ( 0.50 %) ----------------------------------
    INO4 IPv6 only 1 ( 0.10 %) ----------------------------------

    CrashMail capable = 845 ( 85.18 %)
    MailOnly nodes = 313 ( 31.55 %)
    Listed-only nodes = 25 ( 2.52 %)



    [Report produced by NETSTATS - A PD pgm]
    [ Revised by B Felten, 2:203/2]
    [ NetStats 3.8 2014-11-23]

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From Lee Lofaso@2:203/2 to All on Mon Oct 28 12:12:07 2019
    GENERAL ARTICLES


    Why I resigned as FTSC administrator
    By Michiel van der Vlist (2:280/5555) (ex 2:2/20)

    On 1 November 2018, now almost a year ago, I resigned as FTSC administrator. Why?

    Short answer: The fun was gone.

    Long answer:

    The FTSC has always been running behind the facts in that it docu-
    ments current practise created by others instead of creating it
    herself. That was the theory anyway. But at least the situation has
    always been that once something was documented as a standard, it was considered binding. Or at least that POV was supported by the powers
    that be. More precise: the FTSC had the support of the *C structure.

    Uh-oh. Here it comes.

    In the autumn of 2017 something happened that dramatically changed
    that position.

    Drumroll ...

    ZC2 in his infinite wisdom decreed that so called ,MOB nodes were
    welcome in Fidonet. They are mobile nodes running HotdogEd or
    AfterShocK.

    So?

    Presently such nodes can not accept incoming calls in
    almost all mobile networks in Z2. Those nodes have the reachability
    of a point. By accepting such nodes as fully fledged nodes, ZC2
    single handedly changed the requirements for Fidonet membership. He
    did that all by himself without consulting any other Fidonet members.

    IOW, there are no longer any standards. Which means no more trolls.
    Which means we are all sysops. Each and every one of us.

    *1)

    Where it concerned the FTSC is that he also decreed that such nodes
    are to be listed without the Pvt keyword. Like this:

    ,865,Lucas_Visions,Mortsel,Luc_Sienaert,-Unpublished-,300,U,MOB

    So?

    As these nodes are listed without any contact information, they are private nodes as per FTS-5000.005 par 5.3. So they should be listed
    with the Pvt keyword. The Pvt keyword serves to make software aware
    that it should not attempt to connect directly but route mail through
    the hub or host. This mechanism has been in use almost from the start
    of Fidonet.

    Yay! I'm a sysop! Without ever even trying!

    I tried to explain this to the ZC and - mandated by FTA-1001.007 - strongly advised him to drop the wicked idea of listing uncontactable nodes without the Pvt keyword. It fell on deaf ears. The ZC insisted
    they should be listed without Pvt.

    Brilliant ideas are for brilliant minds ...

    At the time of the ZC's decree, Belgium (net 292) and The Netherlands
    (net 280) were united in Region 28. I was RC28 (elected). As a side
    note I should add that net 292 is so big that maintaining its
    nodelist segment and routing the mail seems to be such a gigantic task that it is too much for the NC292 alone to handle. The help of a Hub operator is apparently required. The sysop of Hub 292/80 is Ward
    Dossche. This Hub operator maintains his own section of the nodelist.

    I received a net segment from NC292 with, among other changes, the
    line above. The line was in the segment of Hub 80. I rejected the
    net 292 segment as in violation of FTS-5000. My POV was that these
    nodes do not belong in the nodelist at all but should participate in Fidonet as points. As a compromise however, I offered to have them
    listed as Pvt nodes. The offer was rejected and I was told the FTSC standards are not binding and I was /ordered/ by the ZC to accept and process the net 292 segment as submitted. I refused. A decision based
    on technical grounds as mandated by par. P4 3.8.

    As a result the sysops of net 292 decided they no longer wanted to be
    part of Region 28. Or so I was told by the ZC2. I was not given the opportunity to check with the rest of the sysops of net 292. Region
    29 was reinstated and the new RC29 accepted a net 292 segment with
    ,MOB nodes without the Pvt keyword. Problem solved.

    NOT. This was unacceptable to me. Not the splitting of the region as
    such, but the fact that the FTSC standard was set aside just like
    that by the ZC. By decree.

    It killed my motivation. Against my better judgement I waited a year
    in hope that my motivation would return. But it didn't. The damage
    was done and it was permanent. The drive was gone. I was no longer motivated to spend time and energy on documenting standards that can
    be nullified just like that by decree of the ZC.

    OMG! The ZC grounded The Flying Dutchman! Who'd a thought it
    even possible! This is the end! The end of all! And I forgot
    to repent!

    Fidonet is a hobby. Hobbies are supposed to be fun. For me the fun of documenting standards for Fidonet was gone when I was told by my ZC
    that the documented standards are not binding and when he attempted
    to force me to act in violation of the standards. And when I refused,
    he split up the region in order to get his way. It was not the first
    clash with my ZC but it was the brick that broke the camel's back.
    The damage is permanent and irreversible. The fun was gone, I decided
    I would not waste any more time and energy on the FTSC. Time to move
    on. Hence my resignation as FTSC head honcho.

    Michiel van der Vlist. (2:280/5555) (ex 2:2/20)

    *1) Fidonews 34-37, 11 Sept 2017.

    Well, since there are no more standards, what is the point of being
    a sysop? What is the point of Fidonet at all?

    Thanks for all your time and input, Michiel.

    Now it's back to throw the dog a bone ...

    --Lee

    --
    We Put Big Loads In Tight Places

    --- MesNews/1.08.05.00-gb
    * Origin: news://eljaco.se (2:203/2)