• 2025 FTSC election

    From Rob Swindell@1:103/705 to All on Sun Feb 16 20:58:08 2025
    2025 FTSC standing member election, call for votes
    ==================================================

    Voting for FTSC standing members is open now, from
    Saturday, 15 Feb 2025, 20:00 UTC through Saturday, 08 Mar 2025, 20:00 UTC.

    All RCs are entitled to vote. Each voter may cast one "yes"
    or one "no" vote for each candidate. Voters need not vote for all
    candidates, a non vote will be regarded as "abstain" for that candidate. Candidates must receive more "yes" than "no" votes to be elected.

    Although not required, voters are encouraged to consult their
    constituency before casting their votes. Debate with the candidates
    is also encouraged. No need to hurry.

    No revisions to ballots will be accepted. Voters are urged to consider
    their choices carefully, as they cannot be changed once submitted.

    Voting ends on Saturday, 08 March 2025, 20:00 UTC.

    The status of RC's will be determined by NODELIST.017 of this year
    by the list as issued by the ZC in the zone where they reside.

    The List of nominated and accepted candidates:

    * Deon George (3:633/509), nominated Feb-1 by Jay Harris (RC12)
    * Andrew Leary (1:320/219), nominated Feb-2 by Niels Johcheere (RC29)
    * Tim Schattkowsky (2:2/29), nominated Feb-5 by Fabio Bizzi (RC33)
    * Jason Bock (1:267/310), nominated Feb-8 by Andrew Leary (RC16)

    Voters are requested to copy and paste the form below, mark a
    cross for each candidate in the "yes" or the "no" column for all
    candidates they wish to cast a vote for and post it in FTSC_PUBLIC
    addressed to "Election Coordinator with a subject of "Vote".

    Once again, voters need not vote for all candidates.

    ----------------------------------------------
    | Name | Node nr | Yes| No |
    |----------------------|-------------|----|----|
    | Deon George | 3:633/509 | | |
    | Andrew Leary | 1:320/219 | | |
    | Tim Schattkowsky | 2:2/29 | | |
    | Jason Bock | 1:267/310 | | |
    ----------------------------------------------

    Thank you,

    Rob Swindell
    Standing FTSC Member and stand-in Election Coordinator
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Terry Roati@3:712/1321 to Rob Swindell on Mon Feb 17 16:44:16 2025

    On Feb 16, 2025 09:06pm, Rob Swindell wrote to All:

    2025 FTSC standing member election, call for votes
    ==================================================

    ----------------------------------------------
    | Name | Node nr | Yes| No |
    |----------------------|-------------|----|----|
    | Deon George | 3:633/509 | X | |
    | Andrew Leary | 1:320/219 | X | |
    | Tim Schattkowsky | 2:2/29 | X | |
    | Jason Bock | 1:267/310 | X | |
    ----------------------------------------------

    Regards Terry - RC54

    ... Platinum Xpress & Wildcat!..... Nice!!!!
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
  • From Michiel van der Vlist@2:280/5555 to Rob Swindell on Mon Feb 17 10:19:50 2025
    Hello Rob,

    On Sunday February 16 2025 20:58, you wrote to All:

    The List of nominated and accepted candidates:

    * Deon George (3:633/509), nominated Feb-1 by Jay Harris (RC12)
    * Andrew Leary (1:320/219), nominated Feb-2 by Niels Johcheere (RC29)
    * Tim Schattkowsky (2:2/29), nominated Feb-5 by Fabio Bizzi (RC33)
    * Jason Bock (1:267/310), nominated Feb-8 by Andrew Leary (RC16)


    Tim Schattkowsky does not qualify as a candidate. His message of acceptance did not originate from a node number that lists him as a fidonet sysop.

    Candidates MUST accept by posting a message in FTSC_PUBLIC in
    order to qualify, with the exception of self nominees. The
    message must originate from a node number that has the candidate
    listed as SysOp in NODELIST.040 as issued by the candidate's ZC.

    His message of acceptance originates from 2:310/31.6 and therefore does not comply with the above rule that has been in effect since 2019.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Nick Boel@1:154/700 to Michiel van der Vlist on Mon Feb 17 09:19:34 2025
    Hey Michiel!

    On Mon, 17 Feb 2025 03:19:51 -0600, you wrote:

    His message of acceptance originates from 2:310/31.6 and therefore
    does not comply with the above rule that has been in effect since
    2019.

    Held on to that one since the day he accepted his nomination, didn't you?

    Just chomping at the bit the entire nomination period, waiting for it to end, for your prized "gotchya" moment. When you could have politely pointed out the mistake (even via netmail) and had it corrected before the period was over.

    But no, you'd much rather shove a knife into ones back.

    Regards,
    Nick

    ... He who laughs last, thinks slowest.
    --- SBBSecho 3.23-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
  • From Dan Clough@1:135/115 to Nick Boel on Mon Feb 17 15:14:24 2025
    Nick Boel wrote to Michiel van der Vlist <=-

    His message of acceptance originates from 2:310/31.6 and therefore
    does not comply with the above rule that has been in effect since
    2019.

    Held on to that one since the day he accepted his nomination, didn't
    you?

    Just chomping at the bit the entire nomination period, waiting for it
    to end, for your prized "gotchya" moment. When you could have politely pointed out the mistake (even via netmail) and had it corrected before
    the period was over.

    But no, you'd much rather shove a knife into ones back.

    Yup, agreed. Completely dick-ish move there. Who's surprised?



    ... Computer Hacker wanted. Must have own axe.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Maurice Kinal@1:153/7001.2989 to Dan Clough on Mon Feb 17 21:25:08 2025
    Hey Dan!

    Who's surprised?

    I am shocked and dismayed. Does that count?

    Life is good,
    Maurice

    o- -o o- o- o- o- o- o- o- -o o- o- -o o- o- -o /) (\ /) /) /) /) /) /) /) (\ /) /) (\ /) /) (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
    --- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
    * Origin: One of us @ (1:153/7001.2989)
  • From Michiel van der Vlist@2:280/5555 to Nick Boel on Mon Feb 17 22:14:44 2025
    Hello Nick,

    On Monday February 17 2025 09:19, you wrote to me:

    His message of acceptance originates from 2:310/31.6 and therefore
    does not comply with the above rule that has been in effect since
    2019.

    Held on to that one since the day he accepted his nomination, didn't
    you?

    I responded to the EC's message where he published the list of canditates.

    If you have a problem with the timing, address it to the EC. The EC that did not follow the long ago established custom of responding "immidiately" to nominations and acceptances but who instead remained silent for the entire nomination and acceptance period. It is the EC that created the conditions for this mess to incubate.

    But no, you'd much rather shove a knife into ones back.

    Shooting the messager will not make the problem go away.

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Tim Schattkowsky on Mon Feb 17 13:33:06 2025
    Re: 2025 FTSC election
    By: Michiel van der Vlist to Rob Swindell on Mon Feb 17 2025 10:19 am

    Tim Schattkowsky does not qualify as a candidate. His message of acceptance did not originate from a node number that lists him as a fidonet sysop.

    Hey Tim, you want to resend your acceptance message so that you can prove to everyone that you are who you say you are and that you're capable of using FTN software. :-)

    I'm willing to take the blame for this: I didn't notice this discrepency myself until I was posting the call for votes and thought "meh, no one will notice" - but we have keen eyes for mistakes on the look-out (thank you, these *are* life or death services we're in charge of here)! So please, let's accommodate this late acceptance of the nomination when the candidate touches second base as the rules state they must.

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Dan Clough@1:135/115 to Maurice Kinal on Mon Feb 17 19:56:32 2025
    Maurice Kinal wrote to Dan Clough <=-

    Who's surprised?

    I am shocked and dismayed. Does that count?

    Yep, close enough.



    ... Backup not found: (A)bort (R)etry (P)anic
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Ward Dossche@2:292/854 to Rob Swindell on Wed Feb 19 23:53:42 2025
    Rob,

    Voting for FTSC standing members is open now, from
    Saturday, 15 Feb 2025, 20:00 UTC through Saturday, 08 Mar 2025, 20:00
    UTC.

    Have you reached-out to the RCs so they know they can vote?

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Rob Swindell@1:103/705 to Ward Dossche on Wed Feb 19 15:14:58 2025
    Re: Re: 2025 FTSC election
    By: Ward Dossche to Rob Swindell on Wed Feb 19 2025 11:53 pm

    Rob,

    Voting for FTSC standing members is open now, from
    Saturday, 15 Feb 2025, 20:00 UTC through Saturday, 08 Mar 2025, 20:00 UTC.

    Have you reached-out to the RCs so they know they can vote?

    No, not yet. Any help you can offer there (e.g. name and address list) would be appreciated.
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Ward Dossche@2:292/854 to Rob Swindell on Thu Feb 20 11:51:40 2025
    Rob,

    Have you reached-out to the RCs so they know they can vote?

    No, not yet. Any help you can offer there (e.g. name and address list) would be appreciated.

    Hmmmm ... surely ... one of the best developers in Fidonet knows how to reach RCs ... ?

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Rob Swindell@1:103/705 to Ward Dossche on Thu Feb 20 10:58:42 2025
    Re: Re: 2025 FTSC election
    By: Ward Dossche to Rob Swindell on Thu Feb 20 2025 11:51 am

    No, not yet. Any help you can offer there (e.g. name and address list) would be appreciated.

    Hmmmm ... surely ... one of the best developers in Fidonet knows how to reach RCs ... ?

    I've never had the need. Yes, they're totally discoverable, but getting and parsing a nodelist will have to wait behind the other things I have to do today.
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Wilfred van Velzen on Thu Feb 20 16:15:00 2025
    Re: Re: 2025 FTSC election
    By: Wilfred van Velzen to Rob Swindell on Thu Feb 20 2025 09:59 am

    Hi Rob,

    On 2025-02-19 15:14:59, you wrote to Ward Dossche:

    Have you reached-out to the RCs so they know they can vote?

    No, not yet. Any help you can offer there (e.g. name and address list) would
    be appreciated.

    Have you heard about something called the nodelist? ;-)

    Yeah, of course, though I haven't used one in over 20 years.

    # grep 'Region,' NODELIST.045

    And use the output of that...

    That produces 31 lines without complete addresses, e.g. Region,92,Panama,Pedasi_Panama,John_Dovey,-Unpublished-,300,CM,IBN:gatofuego.sy nchronetbbs.org,PING

    Not directly useful to me, but then I haven't found the nodelist to be useful to me in many years.

    Are there actually 31 RCs?

    Is each supposedly reachable via netmail at <zone>:<region>/1?

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Terry Roati@3:712/1321 to Dan Clough on Fri Feb 21 10:41:46 2025

    On Feb 20, 2025 07:35am, Dan Clough wrote to Ward Dossche:

    To me, the real issue here is: Why would RCs need to be reminded that they can vote on this? Shouldn't every single RC already know that? If they actually don't know that, should they even be an RC?

    Very true but look at when the election is finished how many of the RC's actually voted.

    Terry

    ... Platinum Xpress & Wildcat!..... Nice!!!!
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
  • From Jason Bock@1:267/310 to Ward Dossche on Thu Feb 20 19:56:24 2025
    On <20 Feb, 11:51>, Ward Dossche wrote to Rob Swindell :

    Rob,

    Have you reached-out to the RCs so they know they can vote?

    No, not yet. Any help you can offer there (e.g. name and address list) would be appreciated.

    Hmmmm ... surely ... one of the best developers in Fidonet knows how to reach RCs ... ?

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
    Ward,

    ouch, lol. That was a poke and a touch of kindness. lol

    -Jason

    --- ProBoard v2.32
    * Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)
  • From Nick Boel@1:154/10 to Dan Clough on Thu Feb 20 19:12:58 2025
    Hey Dan!

    On Thu, Feb 20 2025 13:29:42 -0600, you wrote ..

    To me, the real issue here is: Why would RCs need to be reminded that
    they can vote on this? Shouldn't every single RC already know that?
    If they actually don't know that, should they even be an RC?

    1) There's 3 weeks to vote on this. There has been no discussions with any of the candidates, whatsoever. Michiel pointing out everyone else's flaws/mistakes comes with the territory, but doesn't count for anything. He's probably still mad he got voted out of the chair, after having sat on that hat for a very long time, while doing much of nothing.

    2) I'm sure most of the RCs know they can vote on this, but the real question is.. Do they want or care to vote on this? Either way, I'd say about 2/3-3/4 showed up last election and voted. Give it some time.

    The FTSC hasn't done fuck-all in years, not a single proposal raised to a standard (even though some have been in regular use for 20+ years), and the previous few times that proposals have been created and brought to people's attention, there's a small amount that beat on their chests and do everything they possibly can to shut it down.

    Is it worth it?

    Regards,
    Nick

    ... He who laughs last, thinks slowest.
    --- NeoMutt/20250113-dirty
    * Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Jay Harris@1:12/0 to Nick Boel on Thu Feb 20 22:24:50 2025
    On Thursday February 20 2025, Nick Boel said the following...

    2) I'm sure most of the RCs know they can vote on this, but the real question is.. Do they want or care to vote on this? Either way, I'd
    say about 2/3-3/4 showed up last election and voted. Give it some
    time.

    I'll continue to participate though I understand why others don't.

    Is it worth it?

    I think this has been brought up in the past: Couldn't this be a wiki, open to anyone who wants to contribute?

    Find a typo or spelling mistake? Now you can fix it!
    Bored on a rainy Tuesday and want to start documenting something, have at it! Found something that someone started documenting but didn't finish, go nuts!


    Jay

    ... Let him who takes the plunge remember to return it by Tuesday
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: Eastern Canada (1:12/0)
  • From Dan Clough@1:135/115 to Terry Roati on Thu Feb 20 21:51:42 2025
    Terry Roati wrote to Dan Clough <=-

    On Feb 20, 2025 07:35am, Dan Clough wrote to Ward Dossche:

    To me, the real issue here is: Why would RCs need to be reminded that they can vote on this? Shouldn't every single RC already know that? If they actually don't know that, should they even be an RC?

    Very true but look at when the election is finished how many of the
    RC's actually voted.

    Yes, I know that many/most will not. As to why they don't, it would be
    one of the following reasons:

    1. They didn't know they could vote. (I find this unacceptable)
    2. They don't care enough to bother. (Likely the majority of them)
    3. Some care so little that they don't read this echo, and likely don't
    read ANY of the Fido administrative echos. Again I find that
    unacceptable for a person in that position.

    Another factor which would probably make many of them not vote is that
    they (the RCs) don't know anything about the candidates and therefore
    it's hard to know if you'd want them elected. I wish there was more conversations in here by both the prospective candidates and the RCs.

    It's all part of the continuing decline of FidoNet and isn't surprising,
    just disappointing.



    ... Cats remind us that not everything in Nature has purpose.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Dan Clough@1:135/115 to Nick Boel on Thu Feb 20 21:51:42 2025
    Nick Boel wrote to Dan Clough <=-

    To me, the real issue here is: Why would RCs need to be reminded that
    they can vote on this? Shouldn't every single RC already know that?
    If they actually don't know that, should they even be an RC?

    1) There's 3 weeks to vote on this. There has been no discussions with
    any of the candidates, whatsoever. Michiel pointing out everyone else's flaws/mistakes comes with the territory, but doesn't count for
    anything. He's probably still mad he got voted out of the chair, after having sat on that hat for a very long time, while doing much of
    nothing.

    Yes, very disappointing level of discussion, for sure. I know some of
    the history of Michiel... No surprise there.

    2) I'm sure most of the RCs know they can vote on this, but the real question is.. Do they want or care to vote on this? Either way, I'd say about 2/3-3/4 showed up last election and voted. Give it some time.

    Yep, I do know that most of them (that bother) will do so on the last
    day or two.

    The FTSC hasn't done fuck-all in years, not a single proposal raised to
    a standard (even though some have been in regular use for 20+ years),
    and the previous few times that proposals have been created and brought
    to people's attention, there's a small amount that beat on their chests and do everything they possibly can to shut it down.

    Yes, I understand all of this, and again it is very disappointing.

    Is it worth it?

    Not sure what you're asking about here... Is it worth it to vote? Yes,
    I think so. At least it demonstrates that one cared enough to do so,
    and maybe (hopefully) they did some research on candidates to make an
    informed choice on their vote. Probably my statement is more idealistic
    than realistic, but... one can hope. I wish folks would be more
    involved.

    On the other hand, if the FTSC is so far gone that it's actually dead,
    then why bother continuing the charade? Maybe that's what you were
    asking about "worth" there, and in that case I'd answer "probably not".
    Maybe it should just be disbanded and let anarchy take over. But I
    would hope that doesn't happen because it would likely hasten the end of FidoNet.



    ... Dewey, Cheetham, and Howe: Attorneys at Law
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Dan Clough@1:135/115 to Rob Swindell on Thu Feb 20 21:51:42 2025
    Rob Swindell wrote to Wilfred van Velzen <=-

    # grep 'Region,' NODELIST.045

    And use the output of that...

    That produces 31 lines without complete addresses, e.g. Region,92,Panama,Pedasi_Panama,John_Dovey,-Unpublished-,300,CM,IBN:gatof uego.synchronetbbs.org,PING

    Not directly useful to me, but then I haven't found the nodelist to be useful to me in many years.

    Are there actually 31 RCs?

    Yes, there are. The Euro-boys love having entire Regions with grand
    totals of 1-2 nodes in that region. There are 8 RCs in North America.

    Is each supposedly reachable via netmail at <zone>:<region>/1?

    Probably <zone>:<region>/0


    ... Honk if you love BBSing!
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Michiel van der Vlist@2:280/5555 to Nick Boel on Fri Feb 21 11:21:52 2025
    Hello Nick,

    On Thursday February 20 2025 19:12, you wrote to Dan Clough:

    1) There's 3 weeks to vote on this. There has been no discussions with
    any of the candidates, whatsoever. Michiel pointing out everyone
    else's flaws/mistakes comes with the territory, but doesn't count for anything. He's probably still mad he got voted out of the chair, after having sat on that hat for a very long time, while doing much of
    nothing.

    I can understand you not being one of my fans but if you engage in back stabbing please get your facts straight.

    As for me doing much of nothing, I invite everyone to check the author's name on the documents published during my watch. There are a substantial number with either my full name or "FTSC administrator" on it.

    I shall not deny that some of the bumps and bruises I got during that period are still aching at times but me being mad about being voted out of the chair is fake news. I was not voted out of the chair, I resigned of my own initiative.

    As for my issue with Tim, it certainly does count. Him posting from a point number is just the tip of the elephant's trunk. Yes, thee is an elephant in the room and so far no one will mention it or even see it.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Rob Swindell on Fri Feb 21 11:56:32 2025
    Hi Rob,

    On 2025-02-20 16:15:00, you wrote to me:

    Have you heard about something called the nodelist? ;-)

    Yeah, of course, though I haven't used one in over 20 years.

    At all? Isn't synchronet/binkit able to use a nodelist?

    # grep 'Region,' NODELIST.045

    And use the output of that...

    That produces 31 lines without complete addresses, e.g.

    It's all you need to know.

    Region,92,Panama,Pedasi_Panama,John_Dovey,-Unpublished-,300,CM,IBN:gatofuego.s
    y nchronetbbs.org,PING

    You are using an old nodelist! Region,92 was removed from the nodelist on: 27 Nov 2024

    Not directly useful to me, but then I haven't found the nodelist to be useful to me in many years.

    Are there actually 31 RCs?

    Actually there are 30.

    Is each supposedly reachable via netmail at <zone>:<region>/1?

    No, it is: <zone>:<region>/0

    That should work unless their system is misconfigured. In which case it's questionable if they should be a RC. ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nick Boel on Fri Feb 21 12:11:12 2025
    Hi Nick,

    On 2025-02-20 19:12:58, you wrote to Dan Clough:

    To me, the real issue here is: Why would RCs need to be reminded that
    they can vote on this? Shouldn't every single RC already know that?
    If they actually don't know that, should they even be an RC?

    1) There's 3 weeks to vote on this. There has been no discussions with any of
    the candidates, whatsoever.

    I haven't seen you ask any questions to them...

    It's moot anyway as long as the list of candidates is in question.

    Michiel pointing out everyone else's flaws/mistakes comes with the territory, but doesn't count for anything. He's probably still mad he
    got voted out of the chair, after having sat on that hat for a very
    long time, while doing much of nothing.

    You are making stuff up! Michiel resigned as administrator, and didn't bother to get nominated as candidate member for the next election.

    And he is one of few members who actually wrote any documents/proposals at all in the last few decades!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Dan Clough on Fri Feb 21 12:17:56 2025
    Hi Dan,

    On 2025-02-20 21:51:42, you wrote to Nick Boel:

    Yes, very disappointing level of discussion, for sure.

    And how much did you contribute to that?


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Dan Clough on Fri Feb 21 12:21:38 2025
    Hi Dan,

    On 2025-02-20 21:51:42, you wrote to Rob Swindell:

    Are there actually 31 RCs?

    Yes, there are.

    No there are 30.

    The Euro-boys love having entire Regions with grand totals of 1-2
    nodes in that region. There are 8 RCs in North America.

    Did you even bother to check the nodelist before making that claim? There is only one Region (Greece), with 2 nodes in Z2, the others are mostly way bigger. And it isn't like in Z1 where sometimes half to three quarters of the nodes in a region are ghost nodes that are not connectable.

    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Dan Clough on Fri Feb 21 12:41:46 2025
    Hello Dan,

    On Thursday February 20 2025 21:51, you wrote to Nick Boel:

    On the other hand, if the FTSC is so far gone that it's actually dead,

    For all intents and purposes the FTSC is dead. The last document was published in 2022 and it was written by... me.

    Naybe there was nothing noteworthy to document or maybe they just did nothing, Anyweay...

    then why bother continuing the charade?

    Why indeed...

    Maybe that's what you were asking about "worth" there, and in that
    case I'd answer "probably not". Maybe it should just be disbanded and
    let anarchy take over.

    It alway has been anarchy. The FTSC alwas was a toothless tiger. It had a mandate to document "existing practise" - whatever that meant - but it had no means to see that documented standards were followed. And they aren't. There are no consequences for pig headed programmers and *Cs to deviate from FTSC standards. And now that these pig headed programmers have even invaded the FTSC (Rob Swindell, FTS-0009 and Tim Schattkowsky, FTS-5003) we may as abandon all hope.

    But I would hope that doesn't happen because it would likely hasten
    the end of FidoNet.

    Maybe, maybe not.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Dan Clough@1:135/115 to Wilfred van Velzen on Fri Feb 21 08:31:46 2025
    Wilfred van Velzen wrote to Dan Clough <=-

    Yes, very disappointing level of discussion, for sure.

    And how much did you contribute to that?

    Well, nothing. My excuse is that I'm neither a Nominee nor an RC.

    Perhaps it's time that NCs were allowed to contribute/vote?

    Oh..... wait. That might eliminate the majority/control that Zone 2 has
    over the process, with the plethora of RCs located there, so we wouldn't
    want that, right?



    ... All hope abandon, ye who enter messages here.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Michiel van der Vlist@2:280/5555 to Dan Clough on Fri Feb 21 16:54:56 2025
    Hello Dan,

    On Friday February 21 2025 08:31, you wrote to Wilfred van Velzen:

    So here's a question - does every little postage-stamp sized country
    need to be it's own region? In the USA we call those size plots
    "states", and there are multiple states in a Region.

    It is a relic of the past. As you can read in P4, it is based on "areas of convenient calling". In the POTS age calling across a national boundery cost a fortune. Not "convenient". That is why even small countries had their own region. Some still have or have again. Not all of them.

    And it isn't like in Z1 where sometimes half to three quarters
    of the nodes in a region are ghost nodes that are not
    connectable.

    This is unfortunately true, and I'm no happier about that than you
    are.

    I'd rather see aan accurate and up to date nodelist than a nodelist with dead wood. All the nodes listed in R28 are up and running. Contrary to many other regions...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Dan Clough on Fri Feb 21 16:46:00 2025
    Hi Dan,

    On 2025-02-21 08:31:47, you wrote to me:

    Yes, very disappointing level of discussion, for sure.

    And how much did you contribute to that?

    Well, nothing. My excuse is that I'm neither a Nominee nor an RC.

    Anyone can put questions to the nominees. So they can make a well informed advise for their RC how to vote...

    Perhaps it's time that NCs were allowed to contribute/vote?

    That is up to the FTSC and the RC's I suppose...

    Oh..... wait. That might eliminate the majority/control that Zone 2
    has over the process, with the plethora of RCs located there, so we wouldn't want that, right?

    There are more nodes in Z2, so?

    Anyway it probably wouldn't make a difference to the outcome of the elections...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Dan Clough on Fri Feb 21 17:06:00 2025
    Hi Dan,

    On 2025-02-21 08:31:47, you wrote to me:

    So here's a question - does every little postage-stamp sized country
    need to be it's own region?

    Well, yes and no. These regions were all very big in the past, so there was a good reason to create them. Merging them turns out to be a lot more difficult. There are big cultural and language differences between most of them, some are even at war with eachother. Scandinavia did a succesfull merge (so far). Region 28 and 29 tried it for a while, but the former Region 29 sysops weren't happy with the situation and decided to become their own Region again. And there is the catch all Region 56, with a number of small nets for different countries.

    In the USA we call those size plots "states", and there are multiple states in a Region.

    At least you all speak 1 language (mostly).


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From August Abolins@2:221/1.58 to Michiel van der Vlist on Fri Feb 21 19:17:00 2025
    Hello Michiel van der Vlist!

    MvdV> For all intents and purposes the FTSC is dead. The last
    MvdV> document was published in 2022 and it was written by...
    MvdV> me.

    Which one is that?

    MvdV> [...] And now that these pig headed programmers have
    MvdV> even invaded the FTSC (Rob Swindell, FTS-0009 and Tim
    MvdV> Schattkowsky, FTS-5003) we may as abandon all hope.

    Outch.

    I don't see any updates in either fts above.

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Nick Boel@1:154/10 to Dan Clough on Fri Feb 21 19:38:50 2025
    Hey Dan!

    On Fri, Feb 21 2025 03:51:42 -0600, you wrote:

    Is it worth it?

    On the other hand, if the FTSC is so far gone that it's actually
    dead, then why bother continuing the charade? Maybe that's what you
    were asking about "worth" there, and in that case I'd answer
    "probably not". Maybe it should just be disbanded and let anarchy
    take over. But I would hope that doesn't happen because it would
    likely hasten the end of FidoNet.

    Yes, most definitely was referring to this one. ;)

    Regards,
    Nick

    ... He who laughs last, thinks slowest.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Björn Felten@2:203/2 to Wilfred van Velzen on Sat Feb 22 03:07:40 2025
    Wilfred van Velzen -> Dan Clough skrev 2025-02-21 12:21:
    Are there actually 31 RCs?

    Yes, there are.

    No there are 30.

    I guess it's to difficult to just check the weekly report in our weekly newspaper.

    including 4 zones
    30 regions
    157 hosts
    59 hubs
    admin overhead 250 ( 30.60 %)

    It sure seems like a lot of admin overhead for 817 nodes. Maybe we need some Elon Musk and his DOGE here in Fidonet as well?

    --

    Everything happens for a reason. Sometimes the reason is you're stupid and make bad decisions.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to August Abolins on Sat Feb 22 10:18:20 2025
    Hello August,

    On Friday February 21 2025 19:17, you wrote to me:

    Hello Michiel van der Vlist!

    MvdV>> For all intents and purposes the FTSC is dead. The last
    MvdV>> document was published in 2022 and it was written by...
    MvdV>> me.

    Which one is that?

    FTS-4010.0001 dated 24 dec 2022.

    MvdV>> [...] And now that these pig headed programmers have
    MvdV>> even invaded the FTSC (Rob Swindell, FTS-0009 and Tim
    MvdV>> Schattkowsky, FTS-5003) we may as abandon all hope.

    Outch.

    I don't see any updates in either fts above.

    You missed the point. The messages of Rob Swindell violate FTS-0009. The messages of Tim Schattkowsky violate FTS-5003.

    If even (candidate) FTSC members refuse to follow FTSC standards....


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Björn Felten on Sat Feb 22 11:19:06 2025
    Hi Bj”rn,

    On 2025-02-22 03:07:41, you wrote to me:

    No there are 30.

    I guess it's to difficult to just check the weekly report in our weekly newspaper.

    including 4 zones
    30 regions
    157 hosts
    59 hubs
    admin overhead 250 ( 30.60 %)

    It sure seems like a lot of admin overhead for 817 nodes. Maybe we
    need some Elon Musk and his DOGE here in Fidonet as well?

    There isn't a position in Fidonet that can enforce big changes. And if someone tried that probably just speed up the decline of Fidonet...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Sat Feb 22 11:52:02 2025
    Hello Björn,

    On Saturday February 22 2025 03:07, you wrote to Wilfred van Velzen:

    I guess it's to difficult to just check the weekly report in our
    weekly newspaper.

    including 4 zones
    30 regions
    157 hosts
    59 hubs
    admin overhead 250 ( 30.60 %)

    It sure seems like a lot of admin overhead for 817 nodes. Maybe we
    need some Elon Musk and his DOGE here in Fidonet as well?

    If you go through your Fidonews archives you will find two aticles of mine. Each proposing to drop one level of hierarchie. One to drop the Region level and another to drop the zone level.

    I would not mind if you published them again.

    In its present state Fidonet could function very well with less hierarchie. Of course it is not going to happen....


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Ward Dossche@2:292/854 to Dan Clough on Sat Feb 22 14:00:08 2025
    Dan,

    To me, the real issue here is: Why would RCs need to be reminded that
    they can vote on this? Shouldn't every single RC already know that? If they actually don't know that, should they even be an RC?

    Interesting point and you are not really wrong, nor right either.

    Whatever happens, or not, in the FTSC is not a part of an RC-curriculum. One cannot bend the arm of an RC to vote, I once tried and it didn't work.

    So reminding them usually is a good approach. Some will act, some wont.

    The facts of Fido-life these days are that we already must be happy there is somebody willing to be an RC ... the scrapings of the barrel at some times are becoming thin.

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Ward Dossche@2:292/854 to Jason Bock on Sat Feb 22 14:08:10 2025
    Jason,

    ouch, lol. That was a poke and a touch of kindness. lol

    There was no harm intended. As Rob said, he hasn't looked at a nodelist for ages. I appreciate his presence and involvement.

    A netmail to ...

    1:10/0
    1:11/0
    1:12/0
    1:13/0
    1:16/0
    1:17/0
    1:18/0
    1:19/0
    3:54/0
    3:57/0
    4:80/0
    4:88/0
    4:90/0
    4:93/0

    ... will do the trick... ('wink' to Rob)

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Ward Dossche@2:292/854 to Nick Boel on Sat Feb 22 14:11:20 2025
    Nick,

    1) There's 3 weeks to vote on this. There has been no discussions with
    any of the candidates, whatsoever. Michiel pointing out everyone else's flaws/mistakes comes with the territory, but doesn't count for anything. He's probably still mad he got voted out of the chair, after having sat
    on that hat for a very long time, while doing much of nothing.

    1) Michiel was 'not' voted out of the FTSC-chair. He left by his own decision.

    2) Michiel was one of the best and productive FTSC-chairs ever.

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Jason Bock@1:267/310 to Ward Dossche on Sat Feb 22 09:20:30 2025
    Jason,

    ouch, lol. That was a poke and a touch of kindness. lol

    There was no harm intended. As Rob said, he hasn't looked at a nodelist for ages. I appreciate his presence and involvement.

    A netmail to ...

    1:10/0
    1:11/0
    1:12/0
    1:13/0
    1:16/0
    1:17/0
    1:18/0
    1:19/0
    3:54/0
    3:57/0
    4:80/0
    4:88/0
    4:90/0
    4:93/0

    ... will do the trick... ('wink' to Rob)

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

    Ward,
    I know that there is no harm at all. ;)

    I love the contributions to the BBS and related community that Rob has made.

    34 years ago (1991), I started my first BBS. I started with PCBoard then switched to RA, then T.A.G. because I had a friend, Alan Jurison that was a developer of T.A.G. BBS. I saw Synchronet come out and really wanted to run it. It was amazing way back in the 90's.

    I started StormNet with Alan Jurison and Phil Spevak, which helped me more understand Fidonet. We traversed many continents and had some noteable people involved as well.

    I have a strong passion for the BBS/Fidonet communities and respect everyone that has contributed over the years.

    -Jason

    --- ProBoard v2.32
    * Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)
  • From Nicholas Boel@1:154/10 to Michiel van der Vlist on Sat Feb 22 08:08:18 2025
    Hey Michiel!

    On Fri, 21 Feb 2025 11:21:52 +0100, you wrote:

    I can understand you not being one of my fans but if you engage in back stabbing please get your facts straight.

    Only replying in kind, just as you would do (back stabbing, that is).

    As for me doing much of nothing, I invite everyone to check the author's name on the documents published during my watch. There are a substantial number with either my full name or "FTSC administrator" on it.

    You were once very active. Then things got pretty stale for many years. When I got to be a part of as well as witness documents and proposals brought to the table and some trying to be raised to standards (which is the actual job of the FTSC) get completely shot down by you and others, that was the nail in the coffin right there.

    I shall not deny that some of the bumps and bruises I got during that
    period are still aching at times but me being mad about being voted out
    of the chair is fake news. I was not voted out of the chair, I resigned
    of my own initiative.

    Ah, my bad. Must not have been important enough for me to remember. Was that about the time you held an election for yourself and got a bunch of flak for it? This is probably why this election someone you don't 'approve' of was asked to hold it, instead.. so history didn't repeat itself. ;)

    As for my issue with Tim, it certainly does count. Him posting from a
    point number is just the tip of the elephant's trunk. Yes, thee is an elephant in the room and so far no one will mention it or even see it.

    Tim is a current author of software being used in Fidonet, and quite a few people already know that.

    I don't care about your issues with Tim. What disgusted me, was that you most likely noticed this right away, and had the entire time of nominations to point it out, yet you didn't (and I suspect you did that on purpose to prove some kind of point that only you care about). I'm guessing since most people in this echo either know Tim, or know of his software, that where he posted from either went unnoticed or nobody cared (because they knew he has a valid Fidonet node).

    You had other motives, though.

    Regards,
    Nick

    ... He who laughs last, thinks slowest.
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sat Feb 22 08:20:50 2025
    Hey Wilfred!

    On Fri, 21 Feb 2025 12:11:12 +0100, you wrote:

    I haven't seen you ask any questions to them...

    I might not have any questions for them, just like you might not. However, maybe some RCs wait to see if anyone else asks anything or any other discussion goes on before jumping right into voting in the first few days?

    And he is one of few members who actually wrote any
    documents/proposals at all in the last few decades!

    You mean the only one that was able to push them through. He was also one of the few who stopped documents/proposals from getting through, too.. which was more recent than most of the other things done in the last few decades.

    Regards,
    Nick

    ... He who laughs last, thinks slowest.
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Feb 22 15:46:16 2025
    Hi Nicholas,

    On 2025-02-22 08:20:50, you wrote to me:

    And he is one of few members who actually wrote any
    documents/proposals at all in the last few decades!

    You mean the only one that was able to push them through. He was also one of
    the few who stopped documents/proposals from getting through, too..

    I was never part of the FTSC, so I don't know what went on there. But knowing Michiel a bit, I suspect there were very good reasons to stop those documents from getting through.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Ward Dossche@2:292/854 to Dan Clough on Sat Feb 22 16:09:28 2025
    Dan,

    Oh..... wait. That might eliminate the majority/control that Zone 2 has over the process, with the plethora of RCs located there, so we wouldn't want that, right?

    It is total nonsense to believe that zonal balances have anything to do with the functioning of the FTSC. It is about technical competences and right now we have one competent active member and 4 competent candidates some of them (or all?) have already occupied a seat in the FTSC.

    So this election boils down to the question: do we let the FTSC fold or do we keep it intact?"

    So far 2 RCs have voted in favor of continuing.

    As for majority/control over the process ... people should get over this ridiculous idea that power is part of the process. If and when this election concludes, we probably will have 3 members from Z1, 1 from Z2 and 1 from Z3.

    There goes your Z2-majority control down the drain ...


     \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Ward Dossche@2:292/854 to Michiel van der Vlist on Sat Feb 22 16:13:54 2025
    Michiel,

    There are no consequences for pig headed programmers and *Cs to
    deviate from FTSC standards. And now that these pig headed programmers
    have even invaded the FTSC (Rob Swindell, FTS-0009 and Tim Schattkowsky, FTS-5003) we may as abandon all hope.

    I have always found Rob to be very accomodating when I asked/suggested him something ... pig headed?

    Friendly adking helps...

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Dan Clough@1:135/115 to Björn Felten on Sat Feb 22 09:37:16 2025
    Bj”rn Felten wrote to Wilfred van Velzen <=-

    Are there actually 31 RCs?

    Yes, there are.

    No there are 30.

    I guess it's to difficult to just check the weekly report in our
    weekly newspaper.

    including 4 zones
    30 regions
    157 hosts
    59 hubs
    admin overhead 250 ( 30.60 %)

    Yeah...... nothing is ever inaccurate in the "newspaper"...

    Just don't look at the Fido Software section...

    <EYEROLL>



    ... Cats remind us that not everything in Nature has purpose.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Kurt Weiske@1:218/1 to Michiel van der Vlist on Sat Feb 22 08:16:30 2025
    Michiel van der Vlist wrote to BjArn Felten <=-

    If you go through your Fidonews archives you will find two aticles of mine. Each proposing to drop one level of hierarchie. One to drop the Region level and another to drop the zone level.

    I would not mind if you published them again.

    I've posted the same thing - I thought you could get rid of the zone
    politics by making everything one zone, but then people complained about whether it'd be called Zone 1 or Zone 2. :)

    We're starting to see regional attrition, Z1C has consolidated zones
    recently when a RC retired. That might help with some of the
    complication.

    Separate IP-only legacy networks are the biggest complication, I'd think
    - why have a region with a handful of legacy nets with 1-2 nodes and no
    NC? When I first took over R10 I was NC for 5-6 legacy nets that had no separate NC. I took those and moved those into an IP-only net where I
    could (except for one net that's well advertised and nets where people
    wanted to be NC to manage their own net)

    That low-level consolidation cleared up a lot of the complication. If
    everyone did that, from the bottom-up, I think we'd get rid of a lot of
    that overhead.



    --- MultiMail/Win v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/1)
  • From Michiel van der Vlist@2:280/5555 to Ward Dossche on Sat Feb 22 19:53:38 2025
    Hello Ward,

    On Saturday February 22 2025 16:13, you wrote to me:

    There are no consequences for pig headed programmers and *Cs to
    deviate from FTSC standards. And now that these pig headed
    programmers have even invaded the FTSC (Rob Swindell, FTS-0009 and
    Tim Schattkowsky, FTS-5003) we may as abandon all hope.

    I have always found Rob to be very accomodating when I asked/suggested
    him something ... pig headed?

    Yes.

    Friendly adking helps...

    Sometimes it does and sometimes it doesn't. I have done my share of trying to keep the frogs in the wheel barrow. Now that I no longer have any function in Fidonet I can drop the "diplomatics" and just say what is on my mind.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Nick Andre@1:229/426 to Michiel Van Der Vlist on Sat Feb 22 15:29:58 2025

    Sometimes it does and sometimes it doesn't. I have done my share of trying keep the frogs in the wheel barrow. Now that I no longer have any function Fidonet I can drop the "diplomatics" and just say what is on my mind.

    Did those frogs include shoving hilarious inaccurate factoids about IPV6 in Canada down my throat years ago, establishing a nodelist gestapo because "you can" and the endless petulent whining about my zone... or FTSC... or anything?

    Whats on your mind now that we haven't heard already?

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dan Clough@1:135/115 to Kurt Weiske on Sat Feb 22 15:12:58 2025
    Kurt Weiske wrote to Wilfred van Velzen <=-

    There isn't a position in Fidonet that can enforce big changes. And if someone tried that probably just speed up the decline of Fidonet...

    One thing I've been concerned about is if you make a sweeping change
    that requires a change from the downlinks, how many BBSes are running
    on autopilot, and how many sysops would choose to pull the plug instead
    of spending time on something they're effectively done with?

    Some would disappear, indeed. IMHO that's a good thing, and a way to
    cut out some deadwood. Autopilot == Deadwood, in my book.

    I took over R10 in 2012, and even back then with more participation saw roughly 10% of the network that either dropped out or was already gone when we made the switch.

    Nowadays?

    Yup, I would guess it might be closer to 20% that would be gone in the
    new nodelist. I'd rather have a valid/meaningful nodelist than one
    which is full of errors and bloat.

    Might not be a bad thing, since any board that's on auto-pilot probably isn't contributing to anything except the nodelist.

    Exactly.


    ... "He who is without oil, shall cast the first rod."-Compressions 8.7:1.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Rob Swindell@1:103/705 to Wilfred van Velzen on Sat Feb 22 15:23:28 2025
    Re: Re: 2025 FTSC election
    By: Wilfred van Velzen to Rob Swindell on Fri Feb 21 2025 11:56 am

    Hi Rob,

    On 2025-02-20 16:15:00, you wrote to me:

    Have you heard about something called the nodelist? ;-)

    Yeah, of course, though I haven't used one in over 20 years.

    At all?

    Right (and in truth, it's been more than 20 years).

    Isn't synchronet/binkit able to use a nodelist?

    BinkIt does have that feature/option (to read hostnames and port numbers from a nodelist), but I don't use that feature (and I'm not the primary author of BinkIt).

    # grep 'Region,' NODELIST.045

    And use the output of that...

    That produces 31 lines without complete addresses, e.g.

    It's all you need to know.

    Region,92,Panama,Pedasi_Panama,John_Dovey,-Unpublished-,300,CM,IBN:gato fue go.s
    y nchronetbbs.org,PING

    You are using an old nodelist! Region,92 was removed from the nodelist on: 27 Nov 2024

    Confirmed, that was an old nodelist, the latest I have now reports:

    $ grep -c Region, NODELIST.052
    30

    Actually there are 30.

    Is each supposedly reachable via netmail at <zone>:<region>/1?

    No, it is: <zone>:<region>/0

    That should work unless their system is misconfigured. In which case it's questionable if they should be a RC. ;-)

    Thank you, I'll sending netmails post haste.
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555 to Nicholas Boel on Sun Feb 23 10:59:08 2025
    Hello Nicholas,

    On Saturday February 22 2025 08:08, you wrote to me:

    As for me doing much of nothing, I invite everyone to check the
    author's name on the documents published during my watch. There are
    a substantial number with either my full name or "FTSC
    administrator" on it.

    You were once very active. Then things got pretty stale for many
    years. When I got to be a part of as well as witness documents and proposals brought to the table and some trying to be raised to
    standards (which is the actual job of the FTSC)

    No, that is NOT the job of the FTSC. The job of the FTSC is not to automatically raise every submitted proposal to a standard. The job of the FTSC is to document current practise. Some proposals make it to a standard and some do not. If a proposal documents standard practice that has not been covered yet by the FTSC or does it better than existting standards it can be raised to a standard by itself or be incorporated into an existing standard. If it proposes something new or different, the FTSC offers a platform where it can be discussed and an opportunity is given to the submitter to persuade developers to implement his/her ideas into their software. If/when as a result of that proces the proposed /becomes/ current practise the FTSC can raise it to a standard. If it does not become current practise, it does not make it to a standard and remains in the archives for future reference.

    If you think different you have not understood what the job of the FTSC is.

    get completely shot down by you and others, that was the nail in the coffin right there.

    So... it has been over six years since I resigned. If you thought "I did nothing" what stopped you from stepping forward to fill the vacancy that was left after my resignation? What stopped you from showing the Fidonet community that you could do a better job?

    So2... Why are you arguing with me at all? I am not a candidate. Ask the candidates what THEY think the job of the FTSC is or should be.

    I shall not deny that some of the bumps and bruises I got during
    that period are still aching at times but me being mad about being
    voted out of the chair is fake news. I was not voted out of the
    chair, I resigned of my own initiative.

    Ah, my bad. Must not have been important enough for me to remember.

    But you did "remember" that I was voted out That was "important enough"? .

    Was that about the time you held an election for yourself and got a
    bunch of flak for it?

    Have you stopped beating your wife?

    As for my issue with Tim, it certainly does count. Him posting from
    a point number is just the tip of the elephant's trunk. Yes, thee
    is an elephant in the room and so far no one will mention it or
    even see it.

    Tim is a current author of software being used in Fidonet, and quite a
    few people already know that.

    I know that too. I had a point who uses WinPoint. I followed the Winpoint area. That is how I discovered Tim's software is in violation of FTS-5003. I discussed it with him. He refused to make his software FTS-5003 complient. His argument? "My way is better". Hence my "pig headed".

    Being the author of software however is not qualification for FTSC membership all by itself. There is the requirement of "node of good standing".

    I'm guessing since most people in this echo either know Tim, or know
    of his software, that where he posted from either went unnoticed or
    nobody cared (because they knew he has a valid Fidonet node).

    He has NOT. This rule about posting from a node that lists the candidate as a sysop is not something frivolous that came out of thin air. The rule was introduced because of a candidate that posted as a user from the BBS of Janis Kracht and who was shown to NOT have an operational node from which he could send and receive mail.

    This rule serves as a signal to expose such candidates. So far Tim has failed to comply with this rule.

    There is an elephant in the room. Tim does NOT run a fully fledged fidonet node. 2:2/29 is a fake node. There is no contact information in the nodelist. There can not be because WinPoint can only make outgoing calls. Such software is fine for points, but not for "nodes of good standing".

    Node 2:2/29 is a fake node. It can not accept incoming calls.

    You had other motives, though.

    So you say. You saying so does not make it so.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555.1 to Rob Swindell on Sun Feb 23 13:22:24 2025
    Hello Rob,

    On Monday February 17 2025 13:33, you wrote to Tim Schattkowsky:

    Tim Schattkowsky does not qualify as a candidate. His message of
    acceptance did not originate from a node number that lists him as a
    fidonet sysop.

    Hey Tim, you want to resend your acceptance message so that you can
    prove to everyone that you are who you say you are and that you're capable of using FTN software. :-)

    Another week has passed since the window for accepting nominations has closed and Tim has not responded to your request to repost his message of acceptance. I say he had his chance. He does not qualify.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Klein Schnøørd (2:280/5555.1)
  • From Michiel van der Vlist@2:280/5555.1 to Kurt Weiske on Sun Feb 23 14:16:44 2025
    Hello Kurt,

    On Saturday February 22 2025 08:16, you wrote to me:

    If you go through your Fidonews archives you will find two
    aticles of mine. Each proposing to drop one level of hierarchie.
    One to drop the Region level and another to drop the zone level.

    I would not mind if you published them again.

    I've posted the same thing - I thought you could get rid of the zone politics by making everything one zone, but then people complained
    about whether it'd be called Zone 1 or Zone 2. :)

    I would not mind if all the traces of "zones" were completely eradicated from Fidonet. Zones were never correctly implemented technically anyway. But that isn't going to happen of course. My next best option would be to use zone 0. But that would cause a lot of problems I expect. Many implementations use 0 as a signal that a zone number has not been entered yet. Those implementation are not going away. So.. zone 1 will be the logical choice. I could live with it.

    We're starting to see regional attrition, Z1C has consolidated zones recently when a RC retired. That might help with some of the
    complication.

    Yes, that is good.

    Separate IP-only legacy networks are the biggest complication, I'd
    think - why have a region with a handful of legacy nets with 1-2 nodes
    and no NC?

    Why indeed.

    That low-level consolidation cleared up a lot of the complication. If everyone did that, from the bottom-up, I think we'd get rid of a lot
    of that overhead.

    Agreed.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Klein Schnøørd (2:280/5555.1)
  • From Nicholas Boel@1:154/10 to Michiel van der Vlist on Sun Feb 23 07:09:06 2025
    Hey Michiel!

    On Sun, 23 Feb 2025 10:59:08 +0100, you wrote:

    You were once very active. Then things got pretty stale for many
    years. When I got to be a part of as well as witness documents and
    proposals brought to the table and some trying to be raised to
    standards (which is the actual job of the FTSC)

    No, that is NOT the job of the FTSC.

    What part of what I wrote above is not the job of the FTSC?

    The job of the FTSC is not to automatically raise every submitted
    proposal to a standard.

    Where in what I wrote above did I say "automatically"?

    The job of the FTSC is to document current practise.

    If you think different you have not understood what the job of the
    FTSC is.

    Exactly what I was referring to in my comment above, but thank you for the long winded explanation of what I already know.

    Have you stopped beating your wife?

    Not sure where this came from, but if you want to go down that road.. Have you ever been in a relationship with a woman, besides your mother?

    I know that too. I had a point who uses WinPoint. I followed the
    Winpoint area. That is how I discovered Tim's software is in violation
    of FTS-5003. I discussed it with him. He refused to make his software FTS-5003 complient. His argument? "My way is better". Hence my "pig
    headed".

    What if his way _is_ better? Is this not how proposals and improvements are made as more options and technology becomes available?

    Being the author of software however is not qualification for FTSC membership all by itself. There is the requirement of "node of good standing".

    And you know he has one, he just didn't post from it when he accepted his nomination. You stewed on that for the entire nomination process, then waited until it was over to say anything. Most of us knew you were this kind of person, but this one can definitely go down in the record books as one of your finer moments.

    You had other motives, though.

    So you say. You saying so does not make it so.

    Enough people were here to see it for themselves.

    Regards,
    Nick

    ... He who laughs last, thinks slowest.
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Michiel van der Vlist@2:280/5555 to Nicholas Boel on Sun Feb 23 17:32:46 2025
    Hello Nicholas,

    On Sunday February 23 2025 07:09, you wrote to me:

    Exactly what I was referring to in my comment above, but thank you for
    the long winded explanation of what I already know.

    You are welcome. I will not bother you again with explanations of stuff you already claim to know.

    What if his way _is_ better?

    It isn't. That has been established over a decade ago and it is even documented in fts-5003 why it is not better.

    Is this not how proposals and improvements are made as more options
    and technology becomes available?

    No, just ignoring the established standards and going your own way just because you think it is better is not how improvements are made.

    But you already know that of course.

    Being the author of software however is not qualification for FTSC
    membership all by itself. There is the requirement of "node of good
    standing".

    And you know he has one,

    Negative. I know that he does NOT have one.

    were this kind of person, but this one can definitely go down in the record books as one of your finer moments.

    You had other motives, though.

    So you say. You saying so does not make it so.

    Enough people were here to see it for themselves.

    Everyone here could see that the EC confirmed I have a valid point. No response from Tim.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sun Feb 23 15:14:28 2025
    Re: 2025 FTSC election
    By: Michiel van der Vlist to Dan Clough on Fri Feb 21 2025 12:41 pm

    FTSC standards. And now that these pig headed programmers have even invaded the FTSC (Rob Swindell, FTS-0009 and Tim Schattkowsky, FTS-5003) we may as abandon all hope.

    Invaded? I was *asked* to join this committee. And it's not like there's anything of value here to be had by "invading" it.

    The fact that we're all here using and toying with this arcane technology/network still today, decades after any relevancy, means that we're *all* stubborn (pig headed) to a degree, you included. If you meant that as an insult, you failed. This stuff is a hobby, a toy; and I can stubbornly play with my toy as long as I like and won't bullied away by the likes of you. So kindly, and I mean this with the most utmost due respect, go find another sandbox to piss in.

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sun Feb 23 15:21:06 2025
    Re: 2025 FTSC election
    By: Michiel van der Vlist to August Abolins on Sat Feb 22 2025 10:18 am

    The messages of Rob Swindell violate FTS-0009.

    Yeah, that's been debunked:
    https://wiki.synchro.net/faq:misc#ftn_msgid

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Ward Dossche on Sun Feb 23 15:25:26 2025
    Re: Re: 2025 FTSC election
    By: Ward Dossche to Jason Bock on Sat Feb 22 2025 02:08 pm

    There was no harm intended. As Rob said, he hasn't looked at a nodelist for ages. I appreciate his presence and involvement.

    A netmail to ...

    1:10/0
    1:11/0
    1:12/0
    1:13/0
    1:16/0
    1:17/0
    1:18/0
    1:19/0
    3:54/0
    3:57/0
    4:80/0
    4:88/0
    4:90/0
    4:93/0

    Thanks, I sent netmail reminders to those zone 1 node addresses yesterday and now the zone 3 and 4 address today. Thank you,

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Jason Bock@1:267/310 to Rob Swindell on Sun Feb 23 19:27:10 2025
    On <23 Feb, 15:14>, Rob Swindell wrote to Michiel van der Vlist :

    Re: 2025 FTSC election
    By: Michiel van der Vlist to Dan Clough on Fri Feb 21 2025 12:41 pm

    FTSC standards. And now that these pig headed programmers have even
    invaded
    the FTSC (Rob Swindell, FTS-0009 and Tim Schattkowsky, FTS-5003) we
    may as
    abandon all hope.

    Invaded? I was *asked* to join this committee. And it's not like there's anything of value here to be had by "invading" it.

    The fact that we're all here using and toying with this arcane technology/network still today, decades after any relevancy, means that we're *all* stubborn (pig headed) to a degree, you included. If you meant that as an insult, you failed. This stuff is a hobby, a toy; and I can stubbornly play with my toy as long as I like and won't bullied away by the likes of you. So kindly, and I mean this with the most utmost due respect, go find another sandbox to piss in.

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

    Rob,

    Well said!

    -Jason

    --- ProBoard v2.32
    * Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)
  • From Jay Harris@1:12/0 to Rob Swindell on Sun Feb 23 21:14:44 2025
    On Sunday February 23 2025, Rob Swindell said the following...

    There was no harm intended. As Rob said, he hasn't looked at a
    nodelist for ages. I appreciate his presence and involvement.

    A netmail to ...

    1:10/0
    1:11/0
    1:12/0
    1:13/0
    1:16/0
    1:17/0
    1:18/0
    1:19/0
    3:54/0
    3:57/0
    4:80/0
    4:88/0
    4:90/0
    4:93/0

    Thanks, I sent netmail reminders to those zone 1 node addresses
    yesterday and now the zone 3 and 4 address today. Thank you,

    I received your netmail here, addressed to "nc"


    Jay

    ... A city is a large community where people are lonesome together
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: Eastern Canada (1:12/0)
  • From Rob Swindell@1:103/705 to Jay Harris on Sun Feb 23 20:11:42 2025
    Re: Re: 2025 FTSC election
    By: Jay Harris to Rob Swindell on Sun Feb 23 2025 09:14 pm

    I received your netmail here, addressed to "nc"

    Thanks for confirming. Should've been "rc" though. :-)

    -Rob
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Terry Roati@3:712/1321 to Michiel van der Vlist on Mon Feb 24 19:51:58 2025

    On Feb 23, 2025 10:58am, Michiel van der Vlist wrote to Nicholas Boel:

    Hi Michiel,

    MvdV> No, that is NOT the job of the FTSC. The job of the FTSC is not to
    MvdV> automatically raise every submitted proposal to a standard. The job
    MvdV> of the FTSC is to document current practise. Some proposals make it
    MvdV> to a standard and some do not. If a proposal documents standard
    MvdV> practice that has not been covered yet by the FTSC or does it better
    MvdV> than existting standards it can be raised to a standard by itself or
    MvdV> be incorporated into an existing standard. If it proposes something
    MvdV> new or different, the FTSC offers a platform where it can be
    MvdV> discussed and an opportunity is given to the submitter to persuade
    MvdV> developers to implement his/her ideas into their software. If/when as
    MvdV> a result of that proces the proposed /becomes/ current practise the
    MvdV> FTSC can raise it to a standard. If it does not become current
    MvdV> practise, it does not make it to a standard and remains in the
    MvdV> archives for future reference.

    There has always been a confusion on what the FTSC does and hence the reason for the negativity.

    The FTSC comes over as a secret society as nothing is published, it should issue a simple report each year explaing what has been done for the year on Fidonews.

    As for my issue with Tim, it certainly does count. Him posting from
    a point number is just the tip of the elephant's trunk. Yes, thee
    is an elephant in the room and so far no one will mention it or
    even see it.

    You had an opportunity to make your point ealier but you didn't which does not bode well for your intentions and timing, now that Tim's name is on the vote list the RC's will decide.

    MvdV> I know that too. I had a point who uses WinPoint. I followed the
    MvdV> Winpoint area. That is how I discovered Tim's software is in
    MvdV> violation of FTS-5003. I discussed it with him. He refused to make
    MvdV> his software FTS-5003 complient. His argument? "My way is better".
    MvdV> Hence my "pig headed".

    This is for the FTSC to decide which you would expect they looked at and have either ignored it or it is still being looked at. Since you are no longer on the FTSC and feel so strongly about various issues maybe it's time you got someone to nominate you and then see how the RC's vote.

    We all know your very knowledgable and have contributed to Fidonet over the years which is appreciated by many. There are so many outdated rules and protocols no longer followed but Fidonet carries on.

    Terry

    ... Platinum Xpress & Wildcat!..... Nice!!!!
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
  • From Michiel van der Vlist@2:280/5555 to Jason Bock on Mon Feb 24 10:58:22 2025
    Hello Jason,

    How are you doing with IPv6?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Jason Bock@1:267/310 to Michiel van der Vlist on Mon Feb 24 05:35:06 2025
    MvdV> Hello Jason,
    MvdV>
    MvdV> How are you doing with IPv6?
    MvdV>
    MvdV>
    MvdV> Cheers, Michiel
    MvdV>
    MvdV> --- GoldED+/W32-MSVC 1.1.5-b20170303
    MvdV> * Origin: Nieuw Schnøørd (2:280/5555)

    Michiel,

    I really do not use IPV6 personally, except maybe a couple machines in my lab. I have a couple clients that use it internally, usually in some manufacturing environments.

    I thought it would take off much more than it has in the US.

    It would be good for me to start utilizing it more as it is something that I may be forced to use at some point in my profession.

    Do you use IPV6 regularly?

    Thank you,

    Jason

    --- ProBoard v2.32
    * Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)
  • From Michiel van der Vlist@2:280/5555 to Jason Bock on Mon Feb 24 12:26:52 2025
    Hello Jason,

    On Monday February 24 2025 05:35, you wrote to me:

    I really do not use IPV6 personally, except maybe a couple machines in
    my lab. I have a couple clients that use it internally, usually in
    some manufacturing environments.

    So you are an ICT professional?

    I thought it would take off much more than it has in the US.

    It does indeed go a lot slower than I hoped and expected. Not just in he US. The US is actually doing pretty well on the global list.

    It would be good for me to start utilizing it more as it is something
    that I may be forced to use at some point in my profession.

    What has stopped you from making your FidoNet node IPv6 capable?

    Do you use IPV6 regularly?

    Yes. Almost all of my IP traffic goes via IPv6. Personal use only I should add. I have been a pensionado for many years now.

    I have been advocating the use of IPv6 in Fidonet for more than 15 years. The list of IPv6 capable Fidonet nodes that is published weekly in Fidonews now counts 109 nodes.

    I would have expected more. It seems that pioneer spirit that once made Fidonet booming is mostly gone. But maybe 109 out of an estimated 300 active nodes is not all that bad...

    Oh wait. I see why your node does not supprt IPv6...

    + 12:02 [5180] call to 1:267/310@fidonet
    12:02 [5180] trying f310.n267.z1.binkp.net [24.30.241.107]...
    12:02 [5180] connected
    + 12:02 [5180] outgoing session with f310.n267.z1.binkp.net:24554
    [24.30.241.107]
    - 12:02 [5180] OPT MB CRC MD5 CRAM-MD5-16e1ccb99840be034f6da10c1fc5d10e
    + 12:02 [5180] Remote requests MD mode
    - 12:02 [5180] SYS SiliconUnderground - ProBoard / FuNet WHQ
    - 12:02 [5180] ZYZ Jason Bock
    - 12:02 [5180] LOC Rochester, NY
    - 12:02 [5180] NDL CM,IBN
    - 12:02 [5180] TIME 2025/02/24 06:00:57 -5:00
    - 12:02 [5180] VER Internet Rex 2.31 Win32 (binkp/1.1)
    + 12:02 [5180] addr: 1:267/310@fidonet

    You are using Irex. One of the reasons, maybe the main reason, I dropped Irex well over 15 years ago is that it does not support IPv6 and as abandonware it never will. I never regretted switching from Irex to Binkd, changing from AMA to BSO and dropping POTS support with InterMail as collateral damage.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Rob Swindell on Mon Feb 24 14:23:10 2025
    Hello Rob,

    On Sunday February 23 2025 15:21, you wrote to me:

    The messages of Rob Swindell violate FTS-0009.

    Yeah, that's been debunked:
    https://wiki.synchro.net/faq:misc#ftn_msgid

    You have published your arguments of why you believe your mnethod to be "better". You have not disproven my assesment that your method is in violation of FTS-0009.

    I am not saying that your arguments are without merit. That is not my point. My point is that simply ignoring a well established standard and going your own way just because you consider it a better way is the not proper way to introduce something new. Independant of the question if it actually IS "better".

    There is nothing wrong with finding better ways to do things. On the contrary. If you think you have something better bring it to the attention of the Fidonet community. By all means experiment with it. But do NOT go against an established standard! Do not call it MSGID. Call it MSGSIG or whatever, but do NOT use something that is already documented as an existing standard.

    It is not your new method as such that I have poblems with, it is the way you introduce it.

    You published "your way" in a corner of the InterNet that would not normally be visited by Joe Sysop. You have been an FSTC member for many years but you never bothered to file a formal proposal for your way to discern one message from another. You never filed a proposal for an amendment to FTS-0009 either. No, you just did it. Just like that. without concern for what it might break.

    There is no point in spending time and energy to document current practise if anyone can just ignore it and do as (s)he pleases ju8st because (s)he thinks that is "better".


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From August Abolins@2:221/1.58 to Michiel van der Vlist on Mon Feb 24 09:21:00 2025
    Hello Michiel!

    MvdV> I know that too. I had a point who uses WinPoint. I
    MvdV> followed the Winpoint area. That is how I discovered
    MvdV> Tim's software is in violation of FTS-5003. I discussed
    MvdV> it with him. He refused to make his software FTS-5003
    MvdV> complient. His argument? "My way is better". Hence my
    MvdV> "pig headed".

    If ftsc only documents current practice, and anything beyond
    fts-0001 is basically optional for operations/compatibility,
    then the term "violation" is inappropriate.


    MvdV> [...] This rule about posting from a node that lists the
    MvdV> candidate as a sysop is not something frivolous that
    MvdV> came out of thin air. The rule was introduced because of
    MvdV> a candidate that posted as a user from the BBS of Janis
    MvdV> Kracht and who was shown to NOT have an operational node
    MvdV> from which he could send and receive mail.

    Why is an operational node even required? It would seem to be
    more important to have persons who are actually interested in
    doing the work for the ftsc, researching the "common use" out
    there in fidoland and scrutinizing documents. Whether that
    person uses someone else's bbs or operates their own node
    shouldn't make a difference for the task at hand.

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Kurt Weiske@1:218/1 to Dan Clough on Mon Feb 24 09:00:22 2025
    Dan Clough wrote to Kurt Weiske <=-

    I think the term "IP-only" is a legacy thing, actually. Nearly the
    entire FidoNet is IP only now, and there's no reason to have some kind
    of special network for them, or for the few remaining POTS systems.
    That's what nodelist flags and fields are for.

    I agree. Given the size of Fidonet, minus the administrative overhead,
    minus the zombie echoes with no posts kept alive by moderators, and
    minus the autopilot nodes, Fidonet would be a different place.

    In the US, you could theoretically remove nets altogether and still
    have a managaeable regional structure. There may be country-specific
    complications in Z2 I'm not aware of.



    --- MultiMail/Win v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/1)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Mon Feb 24 11:20:48 2025
    Re: 2025 FTSC election
    By: Michiel van der Vlist to Rob Swindell on Mon Feb 24 2025 02:23 pm

    Yeah, that's been debunked:
    https://wiki.synchro.net/faq:misc#ftn_msgid

    You have published your arguments of why you believe your mnethod to be "better". You have not disproven my assesment that your method is in violation of FTS-0009.

    Actually, I did. Maybe read it?
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Maurice Kinal@1:153/7001.2989 to Rob Swindell on Mon Feb 24 19:32:10 2025
    Hey Rob!

    Actually, I did. Maybe read it?

    I've read it twice and still don't see where your document complies with;

    --------------------------------------------------------------------
    ^AMSGID: origaddr serialno

    The originating address should be specified in a form that
    constitutes a valid return address for the originating network. --------------------------------------------------------------------

    ^AMSGID: 32799.ftsc_pub@1:103/705 2c227caf
    ^^^^^^^^^^^^^^^^^^^^^^^^

    The above is not a valid return address that I've ever seen.

    Nice try but I for one have to agree with Michiel on this one and rather than spread your obvious corruption I've opted out for ignoring it as you can readily see by the lack of a REPLY string on my part.

    Life is good,
    Maurice

    o- -o o- o- o- o- o- o- o- -o o- o- -o -o -o -o /) (\ /) /) /) /) /) /) /) (\ /) /) (\ (\ (\ (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
    --- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
    * Origin: One of us @ (1:153/7001.2989)
  • From Dan Clough@1:135/115 to Kurt Weiske on Mon Feb 24 16:12:50 2025
    Kurt Weiske wrote to Dan Clough <=-

    I think the term "IP-only" is a legacy thing, actually. Nearly the
    entire FidoNet is IP only now, and there's no reason to have some kind
    of special network for them, or for the few remaining POTS systems.
    That's what nodelist flags and fields are for.

    I agree. Given the size of Fidonet, minus the administrative overhead,
    minus the zombie echoes with no posts kept alive by moderators, and
    minus the autopilot nodes, Fidonet would be a different place.

    Absolutely.

    In the US, you could theoretically remove nets altogether and still
    have a managaeable regional structure. There may be country-specific
    complications in Z2 I'm not aware of.

    Probably true, as long as the RCs were competent and kept on top of
    things.




    ... Nothing is so smiple that it can't get screwed up.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Jason Bock@1:267/310 to Michiel van der Vlist on Mon Feb 24 18:00:36 2025
    MvdV> Hello Jason,
    MvdV>
    MvdV> On Monday February 24 2025 05:35, you wrote to me:
    MvdV>
    MvdV> JB> I really do not use IPV6 personally, except maybe a couple
    MvdV> machines in
    MvdV> JB> my lab. I have a couple clients that use it internally, usually in MvdV> JB> some manufacturing environments.
    MvdV>
    MvdV> So you are an ICT professional?
    MvdV>
    MvdV> JB> I thought it would take off much more than it has in the US.
    MvdV>
    MvdV> It does indeed go a lot slower than I hoped and expected. Not just in MvdV> he US. The US is actually doing pretty well on the global list.
    MvdV>
    MvdV> JB> It would be good for me to start utilizing it more as it is
    MvdV> something
    MvdV> JB> that I may be forced to use at some point in my profession.
    MvdV>
    MvdV> What has stopped you from making your FidoNet node IPv6 capable?
    MvdV>
    MvdV> JB> Do you use IPV6 regularly?
    MvdV>
    MvdV> Yes. Almost all of my IP traffic goes via IPv6. Personal use only I MvdV> should add. I have been a pensionado for many years now.
    MvdV>
    MvdV> I have been advocating the use of IPv6 in Fidonet for more than 15
    MvdV> years. The list of IPv6 capable Fidonet nodes that is published weekly MvdV> in Fidonews now counts 109 nodes.
    MvdV>
    MvdV> I would have expected more. It seems that pioneer spirit that once made MvdV> Fidonet booming is mostly gone. But maybe 109 out of an estimated 300 MvdV> active nodes is not all that bad...
    MvdV>
    MvdV> Oh wait. I see why your node does not supprt IPv6...
    MvdV>
    MvdV> + 12:02 [5180] call to 1:267/310@fidonet
    MvdV> 12:02 [5180] trying f310.n267.z1.binkp.net [24.30.241.107]...
    MvdV> 12:02 [5180] connected
    MvdV> + 12:02 [5180] outgoing session with f310.n267.z1.binkp.net:24554
    MvdV> [24.30.241.107]
    MvdV> - 12:02 [5180] OPT MB CRC MD5 CRAM-MD5-16e1ccb99840be034f6da10c1fc5d10e MvdV> + 12:02 [5180] Remote requests MD mode
    MvdV> - 12:02 [5180] SYS SiliconUnderground - ProBoard / FuNet WHQ
    MvdV> - 12:02 [5180] ZYZ Jason Bock
    MvdV> - 12:02 [5180] LOC Rochester, NY
    MvdV> - 12:02 [5180] NDL CM,IBN
    MvdV> - 12:02 [5180] TIME 2025/02/24 06:00:57 -5:00
    MvdV> - 12:02 [5180] VER Internet Rex 2.31 Win32 (binkp/1.1)
    MvdV> + 12:02 [5180] addr: 1:267/310@fidonet
    MvdV>
    MvdV> You are using Irex. One of the reasons, maybe the main reason, I
    MvdV> dropped Irex well over 15 years ago is that it does not support IPv6 MvdV> and as abandonware it never will. I never regretted switching from Irex MvdV> to Binkd, changing from AMA to BSO and dropping POTS support with
    MvdV> InterMail as collateral damage.
    MvdV>
    MvdV>
    MvdV> Cheers, Michiel
    MvdV>
    MvdV> --- GoldED+/W32-MSVC 1.1.5-b20170303
    MvdV> * Origin: Nieuw Schnøørd (2:280/5555)
    I have been doing IT for about 30 years. Networking, Virtualization, etc.

    Keeping busy. Thank you to BBSing (since 5th grade) and Fidonet, I became passionate and knew I would love to work with computers. I had my first computer at 3 or 4 (1979/1980). I started with a Texas Instruments TI-99/4 then moved to a TI-994A with an expansion unit. I hada blast!

    I should look into doing more with IPv6 as it has been in the back of my mind for a while.

    -Jason

    --- ProBoard v2.32
    * Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)
  • From Vincent Coen@2:250/1 to Jason Bock on Mon Feb 24 23:43:04 2025

    Hello Jason!

    24 Feb 25 18:00, you wrote to Michiel van der Vlist:


    Keeping busy. Thank you to BBSing (since 5th grade) and Fidonet, I
    became passionate and knew I would love to work with computers. I had
    my first computer at 3 or 4 (1979/1980). I started with a Texas
    Instruments TI-99/4 then moved to a TI-994A with an expansion unit. I
    hada blast!

    I should look into doing more with IPv6 as it has been in the back of
    my mind for a while.

    My experience is a little earlier as my first computer was a IBM 1401 and a 7094 around 1963 as an operator for both. Moved to programming around the same time programming in machine code -> Autocode -> Cobol before also playing with ICL 1501, 1900's and new range 29/39's and lots of others including Burroughs, Honeywell, Univac, Cray, DEC (8/11) Elliot 803 and the very first programmable computer available commercially the EE Leo 3 although technically the Leo 2 was
    one as well but was not made available to purchase.

    There is a wee stack of systems I have missed here.

    My children played with computers in the early 80's with the oldest doing so around 1983/4 on two US imported very large kits, and built by me in the mid 70's before I let them loose on Cromemco Z3 constellations running Cromix (*nix).

    Vincent


    --- Mageia Linux v9 X64/Mbse v1.1.0/GoldED+/LNX 1.1.5-b20240309
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Rob Swindell@1:103/705 to Maurice Kinal on Mon Feb 24 16:54:34 2025
    Re: 2025 FTSC election
    By: Maurice Kinal to Rob Swindell on Mon Feb 24 2025 07:32 pm

    Hey Rob!

    Actually, I did. Maybe read it?

    I've read it twice and still don't see where your document complies with;

    --------------------------------------------------------------------
    ^AMSGID: origaddr serialno

    The originating address should be specified in a form that
    constitutes a valid return address for the originating network. --------------------------------------------------------------------

    ^AMSGID: 32799.ftsc_pub@1:103/705 2c227caf
    ^^^^^^^^^^^^^^^^^^^^^^^^

    The above is not a valid return address that I've ever seen.

    1. That clause you quoted is not a requirement.

    2. That *is* a valid return addresss - send a netmail message to that address and I'll get it.
    --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Jason Bock@1:267/310 to Vincent Coen on Mon Feb 24 20:00:22 2025

    Hello Jason!

    24 Feb 25 18:00, you wrote to Michiel van der Vlist:


    Keeping busy. Thank you to BBSing (since 5th grade) and Fidonet, I became passionate and knew I would love to work with computers. I had my first computer at 3 or 4 (1979/1980). I started with a Texas Instruments TI-99/4 then moved to a TI-994A with an expansion unit. I hada blast!

    I should look into doing more with IPv6 as it has been in the back of
    my mind for a while.

    My experience is a little earlier as my first computer was a IBM 1401 and a
    7094 around 1963 as an operator for both. Moved to programming around the same
    time programming in machine code -> Autocode -> Cobol before also playing with
    ICL 1501, 1900's and new range 29/39's and lots of others including Burroughs,
    Honeywell, Univac, Cray, DEC (8/11) Elliot 803 and the very first programmable
    computer available commercially the EE Leo 3 although technically the Leo 2
    was
    one as well but was not made available to purchase.

    There is a wee stack of systems I have missed here.

    My children played with computers in the early 80's with the oldest doing so
    around 1983/4 on two US imported very large kits, and built by me in the mid
    70's before I let them loose on Cromemco Z3 constellations running Cromix (*nix).

    Vincent


    --- Mageia Linux v9 X64/Mbse v1.1.0/GoldED+/LNX 1.1.5-b20240309
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

    Vincent,

    Very cool. Those were the good old days. ;)

    -Jason

    --- ProBoard v2.32
    * Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)
  • From Dan Clough@1:135/115 to All on Mon Feb 24 21:01:14 2025
    Rob Swindell wrote to Maurice Kinal <=-

    Re: 2025 FTSC election
    By: Maurice Kinal to Rob Swindell on Mon Feb 24 2025 07:32 pm

    Actually, I did. Maybe read it?

    I've read it twice and still don't see where your document complies with;

    --------------------------------------------------------------------
    ^AMSGID: origaddr serialno

    The originating address should be specified in a form that
    constitutes a valid return address for the originating network. --------------------------------------------------------------------

    ^AMSGID: 32799.ftsc_pub@1:103/705 2c227caf
    ^^^^^^^^^^^^^^^^^^^^^^^^

    The above is not a valid return address that I've ever seen.

    1. That clause you quoted is not a requirement.

    2. That *is* a valid return addresss - send a netmail message to that address and I'll get it.


    Game. Set. Match.




    ... White dwarf seeks red giant for binary relationship.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Michiel van der Vlist@2:280/5555.1 to Rob Swindell on Tue Feb 25 09:31:24 2025
    Hello Rob,

    On Monday February 24 2025 11:20, you wrote to me:

    Yeah, that's been debunked:
    https://wiki.synchro.net/faq:misc#ftn_msgid

    You have published your arguments of why you believe your mnethod
    to be "better". You have not disproven my assesment that your
    method is in violation of FTS-0009.

    Actually, I did.

    So you say. Saying so does not make it so.

    Maybe read it?

    I have read it.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Klein Schnøørd (2:280/5555.1)
  • From Michiel van der Vlist@2:280/5555 to August Abolins on Tue Feb 25 11:15:24 2025
    Hello August,

    On Monday February 24 2025 09:21, you wrote to me:

    Why is an operational node even required?

    Valid question but irrelevant regarding the election at hand. The rules presently in force require it. Period.

    Chenging the election rules during an election is a no-no. If you want to change that rule, you have to wait until after the current election.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Kurt Weiske@1:218/1 to Dan Clough on Wed Feb 26 06:06:40 2025
    Dan Clough wrote to Kurt Weiske <=-

    Probably true, as long as the RCs were competent and kept on top of things.

    That's one thing I wish we had - more consistency at the RC level. It's
    a volunteer position, and response times and responses vary. I've helped
    a couple of people when their RC didn't respond to requests, and I know
    Z1C actively assists new and prospective sysops.

    One area of Fidonet structure that's archaic are separate echomail coordinators, it seems like that's a hat most RCs wear now.



    --- MultiMail/Win v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/1)
  • From Dan Clough@1:135/115 to Kurt Weiske on Wed Feb 26 11:07:32 2025
    Kurt Weiske wrote to Dan Clough <=-

    Probably true, as long as the RCs were competent and kept on top of things.

    That's one thing I wish we had - more consistency at the RC level. It's
    a volunteer position, and response times and responses vary. I've
    helped a couple of people when their RC didn't respond to requests, and
    I know Z1C actively assists new and prospective sysops.

    Yes, agreed.

    One area of Fidonet structure that's archaic are separate echomail coordinators, it seems like that's a hat most RCs wear now.

    Not sure I can even remember seeing a "NEC" in the nodelist recently...
    Yeah, doesn't seem like it's needed any more.


    ... Gone crazy, be back later, please leave message.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.23-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Tim Schattkowsky@2:2/29 to Michiel van der Vlist on Thu Feb 27 03:46:10 2025
    //Hello Michiel,//

    on *23.02.2025* at *9:59:08* You wrote in Area *FTSC_PUBLIC*
    to *Nicholas Boel* about *"2025 FTSC election"*.

    Was that about the time you held an election for yourself and got a
    bunch of flak for it?
    MvdV> Have you stopped beating your wife?

    Thanks for the information. I dont think I want to continue to talk to you.

    Regards,
    Tim

    --- WinPoint 415.0
    * Origin: Original WinPoint Origin! (2:2/29)