• FidoNews 36:14 [00/09]: The Front Page

    From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    The F I D O N E W S Volume 36, Number 14 08 Apr 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: Bjrn Felten |
    | ______ _//|| _\ / | |
    | / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
    | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


    Table of Contents
    1. FOOD FOR THOUGHT ......................................... 1
    2. EDITORIAL ................................................ 2
    We choose to change the Policy4 .......................... 2
    3. BEST OF FIDONET .......................................... 3
    A parable ................................................ 3
    4. LIST OF FIDONET IPV6 NODES ............................... 5
    List of IPv6 nodes ....................................... 5
    5. JAMNNTPD SERVERS LIST .................................... 8
    The Johan Billing JamNNTPd project ....................... 8
    6. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 9
    7. SPECIAL INTEREST ......................................... 16
    Statistics from the Fidoweb .............................. 16
    Nodelist Stats ........................................... 17
    8. FIDONEWS INFORMATION ..................................... 19
    How to Submit an Article ................................. 19
    Credits, Legal Infomation, Availability .................. 21

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    FOOD FOR THOUGHT =================================================================

    I know not what weapons World War III will be fought with, but World
    War IV will be fought with sticks and stones.

    -- Albert Einstein --


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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    EDITORIAL =================================================================

    We choose to change the Policy4.

    With those words, I'd like to propose that we actually try to
    change our policy with the smallest of steps. From 4.06 to 4.07 the
    only change was a really minor one (adding "the statement above").
    So from 4.07 to 4.08 could be equally minor.

    The reason for a minor change is that 30 years ago, when the last
    change was made, there were many people around who knew how the change
    should be made. But 30 years later, almost nobody from that time is
    with us anymore. Almost nobody knows anymore how it should be done.

    Making a minor change to Policy4 may be the way to pick up the old
    knowledge of the proper procedure, so that we eventually can make
    major, much needed, changes to the document.


    Ergo, the steps involved would be like this:

    1. The ZCs select an IC.

    2. The 31 RCs agree on a new proposal, needing 16 to make up a
    majority. We had 19 active RCs in the recent FTSC election, so only
    12 were dormant. Maybe the sysops in those regions <see below> can
    wake up some of the dormant RCs even?

    3. From thereon it's just to follow the steps in P4.8.2 to 8.6.

    Here is my proposal for the new 4.08:

    http://eljaco.se/FILES/POLICY4.08

    - - - - -

    RCs not active during the latest FTSC election:

    Z1 Z2 Z3 Z4
    ==== ==== ==== ====
    RC11 RC30 .. RC80
    RC12 RC34 RC90
    RC15 RC42
    RC45
    RC46
    RC48
    RC56


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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    BEST OF FIDONET =================================================================

    A parable
    By: David Rance <2:252/110.1>

    (A 20yo gem, still valid -- Editor's note)

    * Area: ENET.SYSOP
    * Original message from David Rance to Steven Leeman
    * Date: 25 May 99 08:59

    You don't see my point, do you? All you folks can talk about is the
    technical specifications of all that we are doing.

    A parable:

    Fred Fidonet is interested in cars. He has a car. He talks about the
    car. He knows the technical specification of the car. He spends all
    his spare time tinkering with the car and tuning the car. Fred loves
    his car and would be completely lost if he had to sell his car.
    However he never goes out in the car. Fred has two sons who are every
    bit as enthusiatic about the car as Fred is. The trouble is that they
    are always arguing about how to make the car work better. In fact
    their conversation is always about the technical side of the car, and
    sometimes their arguments get quite bitter. Sometimes they can't even
    talk to one another because of the bad feeling when they can't get
    their own way.

    While they are all busy arguing, Fred's wife, Angela, would love to go
    out touring, to see some of the countryside and visit friends. After
    all, she thought, that's what they got the car for. It should improve
    the quality of their lives by enabling them to visit people they
    wouldn't otherwise be able to visit. Fred doesn't want to do that.
    Fred's world revolves around making the car work better and better.
    Yes, he sometimes goes out to visit a car mechanic who will help him
    with the car, but he's forgotten all about what his poor wife wants.

    After a while, Angela gets SO bored that she decides to accept an
    invitation from her neighbour, Ian Internet, to go for a trip in his
    car. Ian isn't so much interested in HOW the car works, but loves to
    travel and meet people. And Angela enjoys her trip so much that she
    accepts further invitations. In the end, Angela (you've guessed it)
    decides to leave Fred and go to live with Ian, because he, like
    Angela, is so much more interested in meeting people and finds Ian's
    attitude to the car so much more sensible. It's not an end in itself,
    it helps people to get to where they want to go.

    And, do you know, Fred didn't even understand why Angela had left him!
    Fred asked his sons how to get Angela to come back. He came to the
    conclusion that she would come back if he got a bigger, flashy, car.
    So he did. But Angela didn't come back. So Fred thought that an even
    bigger, flashier car, would attract Angela back, but he couldn't agree
    with his sons as to which car to get.

    And all this time Angela is getting more and more hooked on Ian's
    lifestyle and is now planning to divorce Fred and marry Ian.

    And Fred is STILL wondering what to do to make his car more attractive
    to Angela!!! Of course, Fred is quite right to take an interest in how
    the car works. But he has missed the point that, however big and
    flashy his car is, Angela is interested only it what it can DO to help
    her get out and meet people.

    Poor Fred! Do you think he will ever get Angela back?

    * Any resemblance between the characters above and the readers of this
    echo is purely intentional!

    Best wishes, David



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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    LIST OF FIDONET IPV6 NODES =================================================================

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

    Updated 24 Mar 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/0 Tommi Koivula T-6in4 he.net f
    7 2:221/1 Tommi Koivula T-6in4 he.net f
    8 2:221/6 Tommi Koivula T-6in4 he.net f
    9 2:5053/54 Denis Mikhlevich Native TTK-Volga
    10 2:5030/257 Vova Uralsky T-6in4 he.net
    11 1:154/10 Nicholas Bol Native Spectrum f
    12 2:203/0 Bjrn Felten T-6in4 he.net
    13 2:280/5006 Kees van Eeten Native Xs4All f INO4
    14 3:712/848 Scott Little T-6RD iiNet f IO
    15 2:5020/545 Alexey Vissarionov Native Hetzner f
    16 1:103/17 Stephen Hurd T-6in4 he.net
    17 2:5020/9696 Alexander Skovpen T-6to4 Westlan
    18 2:301/812 Benoit Panizzon Native IMPNET
    19 2:421/790 Viktor Cizek T-6in4 he.net
    20 2:222/2 Kim Heino Native TeliaSonera
    21 3:633/280 Stephen Walsh Native AusNetServers f
    22 2:463/877 Alex Shuman Native Nline f IO
    23 1:19/10 Matt Bedynek T-6in4 he.net
    24 3:770/1 Paul Hayton T-6in4 he.net
    25 2:5053/58 Alexander Kruglikov Native Aruba S.p.a f
    26 1:103/1 Stephen Hurd Native Choopa
    27 3:633/281 Stephen Walsh Native Internode
    28 2:310/31 Richard Menedetter Native DE-NETCUP f
    29 3:633/410 Tony Langdon Native IINET
    30 2:5005/33 Evgeny Zyatkov Native RUCITYCONNECT f
    31 2:5020/329 Oleg Lukashin Native Comfortel f
    32 2:246/1305 Emil Schuster Native TAL.DE
    33 2:2443/1313 Dirk Astrath Native VOLMARNET
    34 2:2448/4000 Tobias Burchhardt Native DTAG IO
    35 2:331/51 Marco d'Itri Native BOFH-IT
    36 1:214/22 Ray Quinn T-6to4 AT&T f
    37 1:154/30 Mike Miller Native LINODE
    38 1:282/1031 Jeff Smith Native Qwest
    39 2:5083/444 Peter Khanin Native OVH
    40 2:5001/100 Dmitry Protasoff Native Hetzner
    41 2:5059/38 Andrey Mundirov T-6in4 he.net
    42 2:240/5853 Philipp Giebel Native Hetzner
    43 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    44 1:123/10 Wayne Smith T-6in4 he.net
    45 2:5021/46 Dmitry Komissarov Native THEFIRST
    46 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    47 2:5080/102 Stas Degteff T-6to4 Novator
    48 1:135/300 Eric Renfro Native Choopa
    49 1:135/371 Eric Renfro Native Cox Comm
    50 1:103/13 Stephen Hurd Native Choopa
    51 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    52 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    53 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    54 4:902/26 Fernando Toledo T-6in4 he.net
    55 2:400/2992 Avshalom Donskoi Native OVH f PM*1
    56 2:5019/400 Konstantin Kuzov Native LT-LT
    57 2:467/239 Mihail Kapitanov T-6in4 he.net f
    58 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    59 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    60 2:5020/736 Egor Glukhov Native VPSVILLE f
    61 2:280/2000 Michael Trip Native Xs4All
    62 2:230/38 Benny Pedersen Native Linode
    63 2:460/58 Stas Mishchenkov T-6in4 he.net f
    64 1 135/367 Antonio Rivera Native RRSW-V6
    65 2:5020/2123 Anton Samsonov T-6in4 he.net
    66 2:5020/2332 Andrey Ignatov Native ru.rtk
    67 1:340/201 Michael Pierce Native ComCast
    68 2:5005/49 Victor Sudakov T-6in4 he.net
    60 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    70 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    71 1:153/757 Alan Ianson Native TELUS
    72 2:5057/53 Ivan Kovalenko T-6in4 he.net f
    73 2:5020/921 Andrew Savin Native Starlink
    74 2:5010/352 Dmitriy Smirnov Native EkranTV f
    75 2:292/854 Ward Dossche Native Belgacom OO
    76 2:469/122 Sergey Zabolotny Native ARUBA-NET f
    77 2:5053/400 Denis Mikhlevich Native TTK-Volga

    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.
    *1 IPv6 address: 2001:41d0:303:69c6:f1d0:2:400:2992


    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 097

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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    JAMNNTPD SERVERS LIST =================================================================

    The Johan Billing JamNNTPd project

    This is a list of known JamNNTPd servers working. They are essentially
    the modern version of Bulletin Board Systems.

    You connect to them using the newsreader of your choice and you don't
    need any other software installed on your computer -- regardless of
    operating system -- but that favourite mail client of yours.

    Even smart phones can handle this, giving you the opportunity to get
    your daily doses of fidonet on the bus, tram or train on the way to
    your job, school or whatever.


    Updated 2019-02-23


    URL news://eljaco.se
    Join http://fidonews.eu
    NETMAIL Yes, 2:203/2

    URL news://rbb.bbs.fi
    Join Info in group +GETACCESS+
    NETMAIL Yes, 2:221/360

    URL nntp://fidonews.mine.nu
    URL nntps://fidonews.mine.nu
    Join http://fidonews.mine.nu
    NETMAIL Yes, 2:221/6

    URL nntp://news.bytemuseum.org
    nntps://news.bytemuseum.org (secure)
    Join Info in group +ACCCESS&SUPPORT+
    NETMAIL Yes, 1:19/10

    URL nntp://news.pharcyde.org
    Join Info in group, +GETACCESS+
    NETMAIL Yes, 1:154/10

    URL: news.tequilamockingbirdonline.net
    Join mailto:sysop@tequilamockingbirdonline.net
    NETMAIL Yes, 1:266/404

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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    FIDONEWS'S FIDONET SOFTWARE LISTING =================================================================



    =================================================================
    FIDONET SOFTWARE LISTING
    =================================================================

    BBS Software List

    Updated 2019-03-25

    Maintained by Andrew Leary (1:320/219)
    Editors Emeritus: Robert Couture, Janis Kracht,
    Sean Dennis

    M=Mailer T=Tosser B=BBS D=Door C=Comm/Terminal
    P=Points E=Editor I=Internet U=Utility #=Info
    F=TIC/SRIF Processor

    *=Software is available and may be registerable,
    but no longer supported or updated.

    @=Website is operating but is no longer updated.

    ?=Software's updating/support status is unknown.

    O=Software is open source.

    This list contains BBS-related software that is available
    for registration (not necessarily supported), open source
    software and actively developed/supported software by its
    author. Software listed may be available for DOS, Linux,
    OS/2 (eComStation), Windows (16 or 32 bit) and OSX.

    .- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.
    |Software: Author |Type |URL, Contact, Ver, Notes Help Node|
    `- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -'

    ==> FRONT-END/INTERNET MAILERS

    Argus |MI*? |http://www.ritlabs.com/en/products
    | | /argus/
    | | v3.210 on 2001-03-29

    BinkleyTerm XE |MO* |http://btxe.sourceforge.net
    | | 2.60XE Beta-XH7 on 2000-10-22

    BinkD |MI? |http://binkd.grumbler.org
    | | gul@gul.kiev.ua 2:463/68
    | | v.1.0.4
    | | v.1.1a-99 (alpha)
    | | ftp://cvs.happy.kiev.ua/pub/fidosoft
    | | /mailer/binkd/
    | |http://www.filegate.net/r50/aftnbinkd/

    D'Bridge |MTCPE|http://www.dbridgemailer.com
    |I | support@dbridgemailer.com 1:1/130
    Nick Andre | | v3.99 SR 41 on 2019-01-13

    FIDO-Deluxe IP |MPUI |http://www.datenbahn.dd-dns.de/
    | | cdp/fp_deluxe/
    | | v2.4 on 2003-09-26

    FrontDoor, FD/APX: |MITPC|http://www.defsol.se 2:20/4609
    Definite Solutions |E | sales@defsol.se
    | | FD v2.33ml, FD/APX v1.15

    InterMail |MCPE |http://www.Intermail.net 1:220/60
    Dale Barnes | | dalebarnes42@majik.net
    | | IM v2.60 on 2017-08-28

    Husky Project |MTPUI|http://husky.sourceforge.net/
    |EO? | v1.9 RC2 on 2010-04-20

    Taurus |MI |http://www.fidotel.com/public/forums/
    (based on Radius) |? | taurus/index.htm
    | | v5.0 on 2006-06-12
    | |

    T-Mail |MI |http://www.tmail.spb.ru (Russian only)
    |? | v2608 on 2001-12-12

    AfterShock |MTEI |https://play.google.com/store/apps/
    Asvcorp | | details?id=com.asvcorp.aftershock
    Anatoly Vdovichev | | rudi.timmer@gmx.us 2:292/140
    Rudi Timmermans | | v1.6.6 on 2017-11-05

    HotDogEd |E |https://play.google.com/store/apps/
    Sergey Pushkin | | details?id=com.pushkin.hotdoged
    | | v2.13.5 on 2017-03-13 2:5020/2141

    HotDogEd FidoNet |MTI |https://play.google.com/store/apps/
    Provider | | details?id=com.pushkin.hotdoged.fido
    Sergey Pushkin | | v2.13.5 on 2017-03-13 2:5020/2141

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    MAIL TOSSERS

    Crashmail II |TO |http://ftnapps.sourceforge.net/
    | | crashmail.html

    FastEcho |T |http://www.softeq.de/old/Products
    | | /FastEcho/fastecho.html
    | | v1.46.1 on 2007-11-13
    | | Registration keys are free & available
    | | by request from the author

    Fidogate |TUI? |http://www.fidogate.org
    | | v4.4.10 on 2004-08-27
    | |

    FMail |TO |https://sourceforge.net/projects/fmail/
    | | v2.0.1.4 on 2017-04-21

    InterEcho |T |http://www.Intermail.net 1:220/60
    Dale Barnes | | dalebarnes42@majik.net
    | | IE 1.20 on 2017-08-28

    JetMail: JetSys |TU |
    (ATARI ST only) | | v1.01 on 2000-01-01

    Squish |T* |http://www.filegate.net/maximus_bbs/
    | | v1.11R2 on 2009-01-01
    | | Source code available in Maximus BBS
    | | archive: http://maximus.sourceforge.net


    WWIVToss |T |http://www.weather-station.org/wwiv/
    | | v1.51 on 2015-05-23

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    BBS SOFTWARE

    BBBS |BICTM|http://www.bbbs.net 2:22/222
    | | b@bbbs.net
    | | v4.01 on 2007-01-28

    EleBBS |BO*? |http://www.elebbs.com
    | | v0.10.RC1 on 2002-06-09

    Enthral BBS |B |http://enthralbbs.com 1:250/501
    Linux/BSD/OSX | | v0.429/Alpha on 2010-10-14
    | | Fidonet filebone SCENEENT

    Ezycom BBS |BT* |http://www.ezycom-bbs.com 3:690/682
    | | v2.15g2 on 2009-11-16

    GT Power |B |http://www.gtpowerbbs.com/
    | | v19.00

    Hermes II Project |BT |http://www.hermesbbs.com/
    Macintosh-based | | malyn@strangegizmo.com
    | | v3.5.10b3

    Maximus BBS |BO* |http://www.filegate.net/maximus_bbs/
    | | v3.03
    | | Source code available at:
    | | http://maximus.sourceforge.net/

    MBSE BBS |BMTFI|http://sourceforge.net/projects/mbsebbs
    |PO | ajleary@sourceforge.net
    | | v1.0.7.12 on 2019-03-15

    Meltdown BBS |UIO |http://meltdown-bbs.sourceforge.net/
    | | v1.0b on 2004-04-26

    Mystic BBS |BMTCE|http://www.mysticbbs.com
    |IO | v1.12 A43 on 2019-02-01

    NiKom BBS (Amiga) |BO |http://www.nikom.org
    | | v2.3.1 on 2017-07-01

    RemoteAccess BBS |B? |http://www.rapro.com 1:1/120
    | | bfmorse@rapro.com
    | | v2.62.2SW

    Renegade BBS |B |http://renegadebbs.info 1:129/305
    | | v1.10/DOS on 2009-10-03

    Spitfire BBS |B? |http://www.buffalocrk.com/
    | | mdwoltz@buffalocrk.com
    | | v3.7 on 2010-01-01

    Synchronet BBS |BMTIO|http://www.synchro.net 1:103/705
    | | v3.17b on 2019-01-01

    Telegard BBS |B* |
    | | v3.09g2-sp4/mL on 1999-12-19

    WildCat! Interactive |MTBEI|http://www.santronics.com
    Net Server, Platinum| | sales@santronics.com
    Xpress: Santronics | |
    Software, Inc. | | v7.0 AUP 454.5 on 2016-06-23

    WWIV BBS |B |http://www.wwivbbs.org
    | | v5.00 on 2015-12-14

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    TIC PROCESSORS/FILEFIX/SRIF

    Allfix |FIUT |http://www.allfix.com/ 1:140/12
    Bob Seaborn | | v6.0.22 on 2011-01-26

    NEF/pk |F |http://nefpk.8m.com/
    | | v2.45b2 on 2000-03-05

    TinyTIC |FO |http://ftnapps.sourceforge.net
    | | /tinytic.html
    | | 1:120/544

    VIReq |FO |http://ftnapps.sourceforge.net
    | | /vireq.html
    | | 1:120/544

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    BBS DOORS/UTILITIES

    Cheepware |DU |http://outpostbbs.net/cheepware.html
    Sean Dennis | | sysop@outpostbbs.net 1:18/200
    | | Fidonet filebone CH-WARE

    DDS (Doorware |D@ |http://www.doorgames.org
    Distribution System)| | ruth@doorgames.org
    Ruth Argust | |

    Jibben Software |D* |http://www.jibbensoftware.com/
    | | bbs-door-games.cfm
    | | scott@jibben.com
    | | 1995-99 Release dates

    John Dailey Software |DU |http://www.johndaileysoftware.com

    Shining Star |D* |http://www.shiningstar.net/bbsdoors/
    | | nannette@shiningstar.net
    | | Doors are registerable via website

    Sunrise Doors: |D |http://www.sunrisedoors.com
    Al Lawrence | | al@sunrisedoors.com
    | | Tel: (404) 256-9518

    T1ny's Software |DU |http://www.tinysbbs.com/files/tsoft/
    Shawn Highfield | | shighfield@gmail.com 1:229/452
    | | Fidonet filebone CH-WARE

    The Brainex System |D |http://www.brainex.com/brainex_system/
    | | stanley@brainex.com
    | | 1994-99 Releases

    Trade Wars |D* |http://www.eisonline.com/tradewars/
    | | jpritch@eisonline.com
    | | v3.09 (DOS-32) in 2002

    Vagabond Software |DU* |http://vbsoft.dhakota.org
    | | d@dhakota.org
    | | Last update: 2008-04-11

    WWIVEdit |DE |http://www.weather-station.org/wwiv/
    | | v3.0 on 2011-06-27

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    POINT SOFTWARE

    CrossPoint (XP) |P? |http://www.crosspoint.de (German only)
    | | pm@crosspoint.de
    | | v3.12d on 1999-12-22

    FreeXP |P |http://www.freexp.de (German only)
    | | support@freexp.de
    | | v3.42 on 2010-06-27

    FidoIP |PO |http://sourceforge.net/apps/mediawiki
    | | /fidoip/
    | | v.1.0.5 on 2010-12

    OpenXP |PIO |https://sourceforge.net/projects
    | | /openxp5/ 2:240/2188.31
    | |http://openxp.uk Windows/Linux
    | | dev@openxp.uk English/German
    | | v5.0.28 on 2016-09-10

    WinPoint |P? |http://www.winpoint.org
    | | English/German/Spanish
    | | v5 (Beta Release) on 2017-03-17
    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    SYSOP MAIL EDITORS

    GoldEd+ |EO |http://golded-plus.sourceforge.net/
    | | v1.1.5 (Snapshot) on 2015-11-30
    | | NOTE: Unstable versions released often

    SqEd32 |E |http://www.sqed.de 2:2476/493
    | | v1.15 on 1999-12-15
    | | Website is in German and English

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    INTERNET UTILITIES

    Ifmail |UIO |http://ifmail.sourceforge.net
    | | crosser@average.org

    Internet Rex |UI? |http://members.shaw.ca/InternetRex/
    | | telnet://xanadubbs.ca 1:342/806
    | | v2.29 on 2001-10-21

    JamNNTPd |UIO |http://ftnapps.sourceforge.net
    | | /jamnntpd.html
    | | 1:120/544

    Luckygate |UO | ftp://happy.kiev.ua/pub/fidosoft/gate
    | | /lgate
    | | gul@gul.kiev.ua

    MakeNL |UO |http://makenl.sourceforge.net
    | | v3.4.6 on 2016-12-01

    RNtrack |U |http://sourceforge.net/projects
    | | /ftrack-as 2:5080/102
    | |stas_degteff@users.sourceforge.net
    | | v1.32 on 2011-04-29

    TransNet |UIO? |http://www-personal.umich.edu/~mressl/
    | | transnet/index.html
    | | transnet@ressl.com.ar
    | | v2.11 on 2007-09-13

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
    INFORMATIONAL WEBSITES/BBS LISTS

    Telnet/Dialup BBS |# |http://www.telnetbbsguide.com 1:275/89
    Guide | | Maintained by Dave Perrussel
    | | This is probably the most updated BBS
    | | list on the Internet for a general
    | | BBS list.

    Synchronet BBS List |# |http://www.synchro.net/sbbslist.html
    | | Maintained automatically
    | | This list is specifically for
    | | Synchronet-based BBS systems and is
    | | automatically updated nightly.

    The BBS Corner |# |http://www.bbscorner.com
    | | This website is more than just files,
    | | it's an encyclopedia of knowledge for
    | | BBS sysops and people who want to
    | | become sysops. This site is run by
    | | the same person who does the Telnet
    | | BBS Guide.

    BBS Nexus |# |https://bbsnexus.com
    | | This website offers a searchable list
    | | of Telnet BBS's.

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    File Archives:

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    http://archives.thebbs.org
    http://sysopscorner.thebbs.org (site is no longer maintained)
    http://www.simtel.net
    http://www.bbsfiles.com
    http://hobbes.nmsu.edu (OS/2 specific)
    http://www.filegate.net/ (FTP access via port 60721)
    http://www.tinysbbs.com/files/

    Note: Most also provide FTP access (use ftp instead of http above)

    The BBS Software List is published weekly in the FidoNews.

    If you have corrections, suggestions or additions to the information
    above, please contact Andrew Leary with your information via the
    FIDONEWS echo or netmail at 1:320/219.

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

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

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, April 08, 2019 00:07:32
    =================================================================
    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/* 5.4m 8.2m 293 0.8h 2.8h 293
    221/* 2.9m 8.1m 309 5.5h 9.5h 309
    240/* 0.2m 0.2m 8 13.1h 18.7h 8
    280/* 7.2m 17.3m 635 4.7h 8.6h 636
    292/* 3.4m 1.7m 33 1.5h 2.8h 32
    320/* 2.1m 1.9m 336 1.4h 3.3h 336
    502/* 0.7m 0.2m 12 2.3h 3.9h 12

    Sigma 4.8m 12.1m 1626 3.4h 7.5h 1626

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

    Input nodelist nodelist.095
    size 187.9kb
    date 2019-04-05

    The nodelist has 981 nodes in it
    and a total of 1505 non-comment entries

    including 4 zones
    31 regions
    170 hosts
    72 hubs
    admin overhead 277 ( 28.24 %)

    and 106 private nodes
    63 nodes down
    78 nodes on hold
    off line overhead 247 ( 25.18 %)


    Speed summary:

    >9600 = 61 ( 6.22 %)
    9600 = 224 ( 22.83 %)
    (HST = 8 or 3.57 %)
    (CSP = 0 or 0.00 %)
    (PEP = 0 or 0.00 %)
    (MAX = 0 or 0.00 %)
    (HAY = 0 or 0.00 %)
    (V32 = 90 or 40.18 %)
    (V32B = 27 or 12.05 %)
    (V34 = 115 or 51.34 %)
    (V42 = 88 or 39.29 %)
    (V42B = 29 or 12.95 %)
    2400 = 1 ( 0.10 %)
    1200 = 0 ( 0.00 %)
    300 = 695 ( 70.85 %)

    ISDN = 27 ( 2.75 %)

    -----------------------------------------------------
    IP Flags Protocol Number of systems -----------------------------------------------------
    IBN Binkp 738 ( 75.23 %) ----------------------------------
    IFC Raw ifcico 85 ( 8.66 %) ----------------------------------
    IFT FTP 62 ( 6.32 %) ----------------------------------
    ITN Telnet 153 ( 15.60 %) ----------------------------------
    IVM Vmodem 10 ( 1.02 %) ----------------------------------
    IP Other 5 ( 0.51 %) ----------------------------------
    INO4 IPv6 only 1 ( 0.10 %) ----------------------------------

    CrashMail capable = 829 ( 84.51 %)
    MailOnly nodes = 311 ( 31.70 %)
    Listed-only nodes = 25 ( 2.55 %)



    [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 Monday, April 08, 2019 00:07:32
    =================================================================
    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. 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:

    Bjrn 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 Infomation, Availability

    + -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
    | |
    | Editor: Bjrn Felten, 2:2/2 |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    + -- -- -- -- -- -- -- - 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 |
    | articles, vol.no nn, issue ii INPUnnii.ZIP |
    | |
    | On the web: |
    | http://eljaco.se/FILES/fnews/ |
    | http://fidonews.eu/FNEWS/ |
    | |
    | The Snooze *and* the FIDONEWS echo in your newsreader: |
    | news://eljaco.se/FIDONEWS |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

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


    ** 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)
  • From Dale Shipp@1:261/1466 to Fidonews Robot on Monday, April 08, 2019 02:27:00
    On 04-08-19 00:07, Fidonews Robot <=-
    spoke to All about FidoNews 36:14 [02/09]: E <=-

    We choose to change the Policy4.

    1. The ZCs select an IC.

    OK.

    2. The 31 RCs agree on a new proposal, needing 16 to make up a
    majority.

    Actually, what you need is 16 to make a quorum, and then a majority of
    those voting to agree.

    We had 19 active RCs in the recent FTSC election, so only
    12 were dormant. Maybe the sysops in those regions <see below> can
    wake up some of the dormant RCs even?

    Is that called poking the bear? :-}}

    3. From thereon it's just to follow the steps in P4.8.2 to 8.6.

    Here is my proposal for the new 4.08:

    http://eljaco.se/FILES/POLICY4.08

    I downloaded it, and did a fc on the two files. I see that all you are changing is to correct the zone number info for Fidonews editor. That
    is exactly what Frank Vest tried when he made you editor. It fell on
    deaf ears and got no response at all so far as I could see.

    Even if you stirred up enough to put it to a vote with the RCs and then
    with the *Cs, many of them may not bother to vote with the feeling of
    "why bother -- this change fixes nothing."

    In particular, even if it passes, it would not make any other future
    amendments / revision easier.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)


    ... Shipwrecked on Hesperus in Columbia, Maryland. 02:35:04, 08 Apr 2019
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Lee Lofaso@2:203/2 to All on Tuesday, April 09, 2019 01:46:26
    FOOD FOR THOUGHT


    I know not what weapons World War III will be fought with, but World
    War IV will be fought with sticks and stones.

    -- Albert Einstein --

    Ants vs cockroaches. Which side is armed with sticks?
    Which side is armed with stones? Gamblers want to know
    so as to place their bets ...

    --Lee

    --
    It Ain't Payday If It Ain't Nuts In Your Mouth

    --- MesNews/1.08.05.00-gb
    * Origin: news://eljaco.se (2:203/2)
  • From Lee Lofaso@2:203/2 to All on Tuesday, April 09, 2019 01:46:32
    EDITORIAL

    We choose to change the Policy4.

    Why?

    With those words, I'd like to propose that we actually try to
    change our policy with the smallest of steps. From 4.06 to 4.07 the
    only change was a really minor one (adding "the statement above").
    So from 4.07 to 4.08 could be equally minor.

    Why not just start from scratch, rather than recognize what
    has never been legitimately passed and ratified by any zone?

    A shorter, better-written, more up-to-date policy document
    is needed. One that is signed, sealed, and delivered. Not
    done in secret, with nobody knowing who composed it, or
    wrote it. Not one rammed down anybody's throat, but one
    that is open to debate and voted on by all - with sysops from
    each zone voting at a time to pass and ratify.

    The reason for a minor change is that 30 years ago, when the last change was made, there were many people around who knew how the change should be made. But 30 years later, almost nobody from that time is
    with us anymore. Almost nobody knows anymore how it should be done.

    More the reason to do away with old. Completely.

    Making a minor change to Policy4 may be the way to pick up the old knowledge of the proper procedure, so that we eventually can make
    major, much needed, changes to the document.

    The "proper procedure" was never done to begin with! The
    current policy document was never legitimately passed and ratified
    in any zone, so why should it be honored by anybody? Much better
    to scrap it and write a completely new one. From scratch.

    Ergo, the steps involved would be like this:

    1. The ZCs select an IC.

    Any 2 ZCs can sabotage it by refusing to play.

    2. The 31 RCs agree on a new proposal, needing 16 to make up a majority. We had 19 active RCs in the recent FTSC election, so only
    12 were dormant. Maybe the sysops in those regions <see below> can
    wake up some of the dormant RCs even?

    Only 19 RCs are active. Therefore, any 4 RCs can sabotage it
    by refusing to play, as it takes 16 to form a quorum.

    3. From thereon it's just to follow the steps in P4.8.2 to 8.6.

    Why bother to even recognize P4 when you don't have to?
    Better to ignore it completely and start from scratch.

    Here is my proposal for the new 4.08:

    All moot, as no policy change is needed.

    It would save everybody a lot of time, and trouble, to simply
    ignore P4 and write a completely new policy document.

    Ultimate power resides in the sysops themselves. Not in some
    unknown group of writers who concocted the idea of a document
    others are obliged to follow.

    http://eljaco.se/FILES/POLICY4.08

    Fixing a flawed document is not the answer.

    Writing a new policy document, by the sysops themselves,
    is the answer. One that is legitimately passed and ratified,
    in each zone.

    --Lee

    --
    As Good As It Looks

    --- MesNews/1.08.05.00-gb
    * Origin: news://eljaco.se (2:203/2)
  • From Lee Lofaso@2:203/2 to All on Tuesday, April 09, 2019 01:46:39
    (A 20yo gem, still valid -- Editor's note)

    You don't see my point, do you? All you folks can talk about is the technical specifications of all that we are doing.

    A parable:

    Fred Fidonet is interested in cars. He has a car. He talks about the
    car. He knows the technical specification of the car. He spends all
    his spare time tinkering with the car and tuning the car. Fred loves
    his car and would be completely lost if he had to sell his car.

    [..]

    While they are all busy arguing, Fred's wife, Angela, would love to go
    out touring, to see some of the countryside and visit friends. After
    all, she thought, that's what they got the car for. It should improve

    [..]

    Poor Fred! Do you think he will ever get Angela back?

    I was at a boat landing down the bayou talking with friends
    when a woman driving a luxury car calmly drove it into the bayou.
    Then she got out the car (through the window) and started
    walking back to town, which was twenty miles away.

    We all saw what happened, but were too stunned to say anything.
    Before long, the cops showed up, along with her husband. She
    did not deny having done what everybody saw her do. The cops
    then asked her husband if he wanted to press charges, as it was
    his car that she drove into the bayou. He declined, saying it
    was all his fault. He was going to have the car repainted,
    and his wife wanted a new mink coat. So the car had to go.

    We all wondered who had to pay for the tow truck to get
    the car out of the bayou ...

    * Any resemblance between the characters above and the readers of this echo is purely intentional!

    It wasn't me! :)

    --Lee

    --
    Nobody Beats Our Meat

    --- MesNews/1.08.05.00-gb
    * Origin: news://eljaco.se (2:203/2)
  • From Lee Lofaso@2:203/2 to Dale Shipp on Tuesday, April 09, 2019 01:46:51
    Hello Dale,

    We choose to change the Policy4.

    1. The ZCs select an IC.

    OK.

    Any 2 ZC's could gum up the works by refusing to go along.

    2. The 31 RCs agree on a new proposal, needing 16 to make up a
    majority.

    Actually, what you need is 16 to make a quorum, and then a majority of those voting to agree.

    Any 4 RC's could gum up thw works by refusing to play.

    We had 19 active RCs in the recent FTSC election, so only
    12 were dormant. Maybe the sysops in those regions <see below> can
    wake up some of the dormant RCs even?

    Is that called poking the bear? :-}}

    Sometimes it is best to let sleeping bears sleep.

    3. From thereon it's just to follow the steps in P4.8.2 to 8.6.

    Here is my proposal for the new 4.08:

    http://eljaco.se/FILES/POLICY4.08

    I downloaded it, and did a fc on the two files. I see that all you are changing is to correct the zone number info for Fidonews editor. That
    is exactly what Frank Vest tried when he made you editor. It fell on
    deaf ears and got no response at all so far as I could see.

    While Bjrn's intentions may be noble, his idea to fix a flawed
    document is no permanent fix of anything. Better to discard the
    entire thing and write a new one.

    Even if you stirred up enough to put it to a vote with the RCs and then with the *Cs, many of them may not bother to vote with the feeling of
    "why bother -- this change fixes nothing."

    Since P4 was never legitimately passed and ratified in the first
    place, nothing needs to be amended. Just ignore it and move on with
    a new policy document.

    In particular, even if it passes, it would not make any other future amendments / revision easier.

    Then do away with it entirely, putting it where it belongs.
    In the trash heap of history.

    --Lee

    --
    It Ain't Payday If It Ain't Nuts In Your Mouth

    --- MesNews/1.08.05.00-gb
    * Origin: news://eljaco.se (2:203/2)
  • From Dale Shipp@1:261/1466 to BjöRn Felten on Wednesday, April 10, 2019 01:43:00
    On 04-09-19 07:46, Bjrn Felten <=-
    spoke to Dale Shipp about FidoNews 36:14 [02/0 <=-


    correct the zone number info for Fidonews editor. That
    is exactly what Frank Vest tried when he made you editor.

    Did he now?

    That is what he did back then. As I said, it fell on deaf ears and went
    no were.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)


    ... Shipwrecked on Hesperus in Columbia, Maryland. 01:45:10, 10 Apr 2019
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Ward Dossche@2:292/854 to Dale Shipp on Wednesday, April 10, 2019 09:33:21
    correct the zone number info for Fidonews editor. That
    is exactly what Frank Vest tried when he made you editor.

    Did he now?

    That is what he did back then. As I said, it fell on deaf ears and went
    no were.

    Let me put it this way ... I never heard of that ... it must have been a very local / premature attempt.

    When did you become editor, Bjorn ?

    \%/@rd

    --- D'Bridge 3.99 SR41
    * Origin: Ceci n'est pas un courriel (2:292/854)
  • From Björn Felten@2:203/2 to Ward Dossche on Wednesday, April 10, 2019 11:08:26
    Let me put it this way ... I never heard of that ... it must have been a very local / premature attempt.

    Indeed.

    When did you become editor, Bjorn ?

    Between January 7th and 14th 2002.



    ..

    --- 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 Lee Lofaso@2:203/2 to Dale Shipp on Wednesday, April 24, 2019 00:51:33
    Hello Dale,

    2. The 31 RCs agree on a new proposal, needing 16 to make up a
    majority.

    Actually, what you need is 16 to make a quorum, and then a majority of
    those voting to agree.

    Sorry, I was wrong -- Bjrn stated it correctly. Majority of the RCs.

    With only 19 active RCs, the bar is too high for change to be
    possible. Kind of like impeachment/removal from office with the
    president's party controlling both houses of the Congress.

    Actually much higher - 16 out of 19. A near impossibility.

    --Lee

    --
    Everybody Loves Our Buns

    --- MesNews/1.08.05.00-gb
    * Origin: news://eljaco.se (2:203/2)
  • From Björn Felten@2:203/2 to Dale Shipp on Tuesday, April 09, 2019 07:46:07
    correct the zone number info for Fidonews editor. That
    is exactly what Frank Vest tried when he made you editor.

    Did he now?




    ..

    --- 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 Dale Shipp@1:261/1466 to Dale Shipp on Tuesday, April 09, 2019 01:09:04
    On 04-08-19 02:27, Dale Shipp <=-
    spoke to Fidonews Robot about Re: FidoNews 36:14 [02/0 <=-


    2. The 31 RCs agree on a new proposal, needing 16 to make up a
    majority.

    Actually, what you need is 16 to make a quorum, and then a majority of those voting to agree.

    Sorry, I was wrong -- Bjrn stated it correctly. Majority of the RCs.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)


    ... Shipwrecked on Hesperus in Columbia, Maryland. 01:11:17, 09 Apr 2019
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Ward Dossche@2:292/854 to Lee Lofaso on Tuesday, April 09, 2019 10:05:45
    Why not just start from scratch...

    Why not just shut up.

    Any 2 ZCs can sabotage it by refusing to play.

    Accusing ZCs of sabotaging Fidonet? I understand why you don't want a nodenumber, even for a very short period of time before you're chased-out again.

    Only 19 RCs are active.

    You don't know that.

    \%/@rd

    --- D'Bridge 3.99 SR41
    * Origin: Ceci n'est pas un courriel (2:292/854)