• FidoNews 42:41 [00/07]: The Front Page

    From FidoNews Robot@2:2/2 to All on Mon Oct 13 00:15:40 2025
    The F I D O N E W S Volume 42, Number 41 13 Oct 2025 +--------------------------+-----------------------------------------+
    | |The newsletter of the | | |
    | | FidoNet community. | | Netmail attach to (POTS): |
    | | Est. 1984 | | 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__| / \// | Publisher: Bj”rn Felten |
    | ______ _//|| _\ / | |
    | / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
    | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


    Table of Contents
    1. JAMNNTPD SERVERS LIST .................................... 1
    The Johan Billing JamNNTPd project ....................... 1
    2. LIST OF FIDONET IPV6 NODES ............................... 2
    List of IPv6 nodes ....................................... 2
    3. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 5
    4. SPECIAL INTEREST ......................................... 13
    Statistics from the Fidoweb .............................. 13
    Nodelist Stats ........................................... 14
    5. FIDONEWS INFORMATION ..................................... 16
    How to Submit an Article ................................. 16
    Credits, Legal Information, Availability ................. 18
    6. EDITORIAL ................................................ 19
    Don't get keyboard crazy ................................. 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 13 00:15:40 2025
    =================================================================
    LIST OF FIDONET IPV6 NODES =================================================================

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

    Updated 12 Oct 2025


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen T-6in4 he.net f
    2 2:280/5003 Kees van Eeten Native KPN/Ziggo f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo/Delta f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 1:154/10 Nicholas Boel Native Spectrum f
    9 2:203/0 Bjorn Felten Native Bahnhof
    10 2:280/5006 Kees van Eeten Native KPN f INO4
    11 3:712/848 Scott Little T-6in4 he.net f
    12 1:103/17 Stephen Hurd T-6in4 he.net
    13 2:5020/9696 Alexander Skovpen T-6in4 IP4Market
    14 2:421/790 Viktor Cizek Native JON.CZ Network
    15 2:222/2 Kim Heino Native TeliaSonera
    16 3:633/280 Stephen Walsh Native AusNetServers f
    17 1:19/10 Matt Bedynek T-6in4 he.net
    18 3:770/1 Paul Hayton Native VETTA
    19 3:770/100 Paul Hayton Native VETTA
    20 2:5053/58 Alexander Kruglikov Native ER-Telecom f
    21 1:103/1 Stephen Hurd Native Choopa
    22 3:633/281 Stephen Walsh Native Internode
    23 2:310/31 Richard Menedetter Native DE-NETCUP f
    24 3:633/410 Tony Langdon Native IINET
    25 2:5020/329 Oleg Lukashin Native Comfortel f
    26 2:331/51 Marco d'Itri Native BOFH-IT
    27 1:154/30 Mike Miller Native LINODE
    28 2:5001/100 Dmitry Protasoff Native Layer7 Networks
    29 2:5059/38 Andrey Mundirov T-6in4 he.net f
    30 2:5083/444 Peter Khanin Native OVH
    31 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f
    32 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    33 1:103/13 Stephen Hurd Native Choopa
    34 2:5020/1042 Stas Mishchenkov Native KCT f
    35 2:5019/400 Konstantin Kuzov Native JSC IOT
    36 2:463/1331 Andrei Dzedolik Native DigitalOcean
    37 2:5010/275 Evgeny Chevtaev T-6in4 IP4Market f
    38 2:280/2000 Michael Trip Native KPN DOWN
    39 2:230/38 Benny Pedersen Native Linode
    40 2:460/58 Stas Mishchenkov Native KCT f
    41 2:5101/1 Andrey Ignatov Native HETZNER
    42 2:5005/49 Victor Sudakov T-6in4 he.net f
    43 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    44 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    45 2:292/854 Ward Dossche Native Proximus
    46 2:469/122 Sergey Zabolotny T-6in4 he.net f
    47 2:5053/400 Alexander Kruglikov Native FirstVDS f
    48 2:5030/1997 Alexey Fayans T-6in4 he.net
    49 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    50 2:240/502 Ludwig Bernhartzeder Native DTAG
    51 2:423/39 Karel Kral Native HOSTUP f
    52 2:280/1049 Simon Voortman Native Solcon
    53 2:335/364 Fabio Bizzi Native OVH
    54 1:124/5016 Nigel Reed Native DAL1-US f
    55 1:229/664 Jay Harris Native Rogers f
    56 2:280/2030 Martien Korenblom Native Transip
    57 3:633/509 Deon George Native Telstra
    58 2:5020/4441 Yuri Myakotin Native SOVINTEL
    59 1:320/319 Andrew Leary Native Comcast f
    60 2:240/5824 Anna Christina Nass Native DTAG f
    61 2:460/5858 Stas Mishchenkov Native KCT f INO4
    62 2:301/812 Benoit Panizon Native WOODYV6
    63 1:229/616 Vasily Losev Native Hostodo
    64 2:301/113 Alisha Stutz T-6in4 he.net
    65 1:153/7715 Dallas Hinton Native Shaw Comms
    66 1:218/840 Morgan Collins Native Linode
    67 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    68 2:240/1634 Hugo Andriessen Native Vodafone
    69 2:280/2040 Leo Barnhoorn Native KPN f
    70 2:5020/736 Egor Glukhov Native RUWEB f
    71 2:221/10 Tommi Koivula Native Hetzner f INO4
    72 1:218/850 John Nicpon Native LINODE-US
    73 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    74 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    75 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    76 1:103/705 Rob Swindell Native Spectrum f
    77 1:134/303 Travis Mehrer Native Shaw Comms
    78 2:5057/19 Max Vasilyev Native ER-Telecom f
    79 2:5075/35 Eugene Subbotin Native RUWEB f
    80 2:5075/37 Andrew Komardin Native IHC
    81 2:550/278 Vladislav Muschinskikh Native FirstByte
    82 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f
    83 2:5020/715 Alex Barinov T-6in4 he.net f
    84 1:16/201 Sergey Myasoedov Native Amazon
    85 1:104/117 Vitaliy Aksyonov Native LLC
    86 2:5030/1340 Dmitry Afanasiev T-6in4 TUNNEL-BROKER-NET
    87 2:221/360 Tommi Koivula Native Elisa f
    88 2:5031/25 Alex Kazankov Native VDSINA
    89 4:902/26 Fernando Toledo Native Claro
    90 2:280/2050 Floris van Unen Native Azure
    91 2:280/2060 Dennis Slagers Native Ziggo f
    92 1:266/625 Scott Street Native Verizon
    93 2:5020/5452 Alex Barinov T-6in4 he.net
    94 2:5030/723 Alexey Khromov Native RU-AI-20240222
    95 3:633/2744 Deon George Native EXETEL-AU
    96 4:930/1 David Gonzalez Native EPMNET
    97 3:633/267 Andrew Clarke Native widebandnetv6 OO
    98 2:463/877 Alex Shuman Native UA-WEBBER f
    99 2:5030/1520 Ekaterina Geyko T-6in4 he.net f
    100 2:201/127 Sergey Semernin Native Obenetwork
    101 2:2448/400 Tobias Burchhardt Native DTAG
    102 2:240/5853 Philipp Giebel Native Hetzner
    103 2:5080/172 Stas Vlasov Native Internet Pro LLC
    104 2:343/107 Enric Lleal Native Hetzner
    105 1:128/10 Jordan McGilvray Native DigitalOcean
    106 2:421/7902 Viktor Cozek Native JON.CZ Network
    107 2:5020/1313 Sergey Efimoff T-6in4 he.net
    108 1:16/201 Sergey Myasoedov Native Amazon
    109 1:135/220 Wayne Smith t-6in4 he.net



    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.
    Example: ::f1d0:2:280:5555 (for node 2:280/5555)
    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.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    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 when compiled with AF_FORCE=1). 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 285


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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Oct 13 00:15:40 2025
    =================================================================
    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

    221/* 3.1m 9.2m 22 0.0h 0.0h 22
    280/* 1.3m 3.8m 902 5.2h 6.9h 903
    292/* 0.8m 0.4m 2
    320/* 2.3m 1.0m 513 1.8h 8.4h 511

    Sigma 1.7m 3.3m 1439 3.9h 7.6h 1437

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

    Input nodelist nodelist.283
    size 154.3kb
    date 2025-10-10

    The nodelist has 818 nodes in it
    and a total of 1198 non-comment entries

    including 4 zones
    30 regions
    158 hosts
    59 hubs
    admin overhead 251 ( 30.68 %)

    and 79 private nodes
    17 nodes down
    33 nodes on hold
    off line overhead 129 ( 15.77 %)


    Speed summary:

    >9600 = 16 ( 1.96 %)
    9600 = 76 ( 9.29 %)
    (HST = 2 or 2.63 %)
    (CSP = 0 or 0.00 %)
    (PEP = 0 or 0.00 %)
    (MAX = 0 or 0.00 %)
    (HAY = 0 or 0.00 %)
    (V32 = 43 or 56.58 %)
    (V32B = 0 or 0.00 %)
    (V34 = 50 or 65.79 %)
    (V42 = 42 or 55.26 %)
    (V42B = 0 or 0.00 %)
    2400 = 1 ( 0.12 %)
    1200 = 0 ( 0.00 %)
    300 = 725 ( 88.63 %)

    ISDN = 15 ( 1.83 %)

    -----------------------------------------------------
    IP Flags Protocol Number of systems -----------------------------------------------------
    IBN Binkp 702 ( 85.82 %) ----------------------------------
    IFC Raw ifcico 59 ( 7.21 %) ----------------------------------
    IFT FTP 34 ( 4.16 %) ----------------------------------
    ITN Telnet 93 ( 11.37 %) ----------------------------------
    IVM Vmodem 11 ( 1.34 %) ----------------------------------
    IP Other 1 ( 0.12 %) ----------------------------------
    INO4 IPv6 only 5 ( 0.61 %) ----------------------------------

    CrashMail capable = 749 ( 91.56 %)
    MailOnly nodes = 241 ( 29.46 %)
    Listed-only nodes = 19 ( 2.32 %)



    [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 FidoNews Robot@2:2/2 to All on Mon Oct 13 00:15:40 2025
    =================================================================
    FIDONEWS INFORMATION =================================================================

    How to Submit an Article

    If you wish to submit an article for inclusion in the Fidonews, here
    are some guidelines, if you send it as an attached file; the preferred
    method if you want reasonable control over how the published article
    will appear in the Fidonews:

    a) Plain text. If you could type it on your keyboard, it's probably
    quite OK. TABs (ASCII 09) are not allowed -- there's no knowing
    how long you've set your tab markings. No line may be longer
    than 70 characters.

    b) Put a title to the article. Put the title in two times. The first
    time, on the first line, with an * before it. The second time, on
    the second line, without the * and centered. This will help in the
    format since the title with the * is removed and used in the index,
    the second line will become the headline. On the third line, put
    your name and FidoNet address, present or former. If former, you
    may want to add some other address where you can be reached for
    personal comments.

    c) Deadline for article submission is Sunday, 22:00 UTC.


    In case a) and b) above is not crystal clear, here's an excellent
    summary by Ward Dossche, a major article contributor:

    Piece of cake:

    1) Ascii text
    2) Line length of 70
    3) Put this at the very top:

    *The title of your text
    The title of your text
    Your Name - Your Nodenumber

    The title is there twice, the line with the * is how it will be
    visible in the table of content.


    Help the Editor by following the above guides. Below are some subjects
    and the file extension for the article as set in the configuration
    file for the making of the Fidonews. Please help by putting the file
    extension of the correct subject on the file name if known.

    Ideas for Subject areas:

    Subject File | Subject File ----------------------------------|----------------------------------
    From the *C's *.css | Rebuttals to articles *.reb
    Fidonet Regional News *.reg | Fidonet Net News *.net
    Retractions *.rtx | General Fidonet Articles *.art
    Guest Editorial *.gue | Fidonet Current Events *.cur
    Fidonet Interviews *.inv | Fidonet Software Reviews *.rev
    Fidonet Web Page Reviews *.web | Fidonet Notices *.not
    Getting Fidonet Technical *.ftc | Question Of The Week *.que
    Humor in a Fido Vein *.hfv | Comix in ASCII *.cmx
    Fidonet's Int. Kitchen *.rec | Poet's Corner *.poe
    Clean Humor & Jokes *.jok | Other Stuff *.oth
    Fidonet Classified Ads *.ads | Corrections *.cor
    Best of Fidonet *.bof | Letters to the Editor *.let

    If you don't know or are not sure, send the article anyway. Put a .TXT
    on it and I'll try to figure out where it should be in the Fidonews.

    If you follow these simple guidelines, there should be little problem
    in getting your article published. If your submission is too far out
    of specs for the Fidonews, it will be returned to you and/or a message
    sent informing you of the problem. This DOES NOT mean that your
    article is not accepted. It means that there is something in it that I
    can not fix and I need your help on it.

    Send articles via e-mail or netmail, file attach or message to:

    Bj”rn Felten
    Fidonet 2:2/2 or 2:203/0
    E-Mail b @ felten dot se
    Skype file bfelten

    IMPORTANT! If you send the article via e-mail, make sure you put the
    word "fidonews" somewhere in the subject line! That way it
    will always pass the spam filter, ending up in the proper
    folder.

    Please include a message, telling me that you have sent an article.
    That way I will know to look for it.


    -----------------------------------------------------------------
    Credits, Legal Information, Availability

    + -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
    | |
    | Editor: Bj”rn Felten, 2:2/2 |
    | |
    | The IPv6 list: Michiel van der Vlist, 2:280/5555 |
    | The S/W list: Andrew Leary, 1:320/219 |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    + -- -- -- -- -- -- -- - EDITORS EMERITI - -- -- -- -- -- -- -- +
    | |
    | Tom Jennings, Thom Henderson, Dale Lovell, Vince |
    | Perriello, Tim Pozar, Sylvia Maxwell, Donald Tees, |
    | Christopher Baker, Zorch Frezberg, Henk Wolsink, |
    | Doug Meyers, Warren D. Bonner, Frank L. Vest |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    Fidonews is published weekly by and for the members of Fidonet.
    There is no copyright attached to Fidonews, though authors
    retain rights to their contributed articles. Opinions expressed
    by the authors are strictly their own. Noncommercial duplication
    and distribution within Fidonet is encouraged. Authors are
    encouraged to send their articles in ASCII text to the Editor
    at one of the addresses above.

    The weekly edition of Fidonews is distributed through the file
    area FIDONEWS, and is published as echomail in the echo FIDONEWS.

    The different articles are distributed in the file area SNOOZE.
    A service to various projects for making Fidonews available on
    the web with a more pleasing lay-out.

    These sources are normally available through your Network
    Coordinator. The current and past issues are also available from
    the following sources:

    + -- -- -- -- -- -- - FIDONEWS AVAILABILITY - -- -- -- -- -- -- +
    | |
    | File request from 2:2/2 or 2:203/0: |
    | current issue FIDONEWS |
    | back issue, volume v, issue ii FNEWSvii.ZIP |
    | or FNEWTvii.ZIP |
    | articles, vol.no nn, issue ii INPUnnii.ZIP |
    | |
    | On the web: |
    | http://eljaco.se/FILES/fnews/ |
    | |
    | The FIDONEWS echo in your newsreader: |
    | news://eljaco.se/FIDONEWS |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Oct 13 00:15:40 2025
    =================================================================
    EDITORIAL =================================================================

    Don't get keyboard crazy
    By Bj”rn Felten
    First published 21 Jan 2002

    When on the streets in a car, you've probably encountered what's often
    referred to as street crazy. This is what people so easily get, when
    something happens. Someone bumps into your car, and suddenly you can
    find yourself in a highly animated discussion with the other driver,
    that often can develop into a nasty situation with violent, and, even,
    in countries where there's a handgun in every glove compartment, fatal
    results.

    How come then, that if you bump into that same person, walking on
    the pavement (that's sidewalk to some of you), there almost never
    develops a case of pavement craziness? In just a split second both
    parties resolve the potential conflict, and all is well.

    The simple explanation is body language. When you accidentally bump
    into someone, you know exactly what to do with your face, shoulders,
    arms and the rest of the body, to immediately apologise. And the
    amazing thing is, that this language seems to be highly universal. It
    works in London, Paris and Berlin as well as in Tokyo, New York and
    Rio de Janeiro.

    But when you sit tucked away in a car, with only your face showing,
    and sometimes not even that, behind shining or even dark windscreens,
    you don't have access to this powerful language. At best, all you have
    is the finger, and that's not the best way to start a discussion...

    Now take our means of communication, here in Fidonet, the written
    word. Ask any good actor to read a couple of lines, taken out of a
    greater context, and he'll tell you it's impossible to know how to
    read them. They can be read in a thousand different ways, giving them
    a thousand different meanings.

    This is what we're up against, when we read mail, echo- as well as
    netmail. We see the written words, but without the proper body
    language to go with those words, and without being able to hear the
    writer saying them in the way they were intended (high, low, funny,
    serious, fast, slow etc.) we lack probably 90% of the information
    needed to fully understand the message.

    So why are we then so fast to reply to those words, in the way many
    do: with invectives, insults and other bashings? Well, to the best
    of my experience, it's often people with the most incredible
    experience of participating in mostly sysop echoes (I think those
    echoes are the worst ones in this respect) that are the worst
    offenders. Maybe they are so used to almost every message being an
    attack on them personally, that they automatically jump to the worst conclusion?

    The remedy is of course, to try to have sysops meeting in person,
    where they can make full use of their body language and voices. After
    such a SupCon or whatever, things have always cooled down considerably
    among the participants. That's a proven fact. So let's all join in on
    a wish for more SupCon's to the people!


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


    ** Prepared for FIDONEWS by Azure/NewsPrep 3.0
    (c) Copyright 1996-1999 Peter Karlsson

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)