I would like to nominate Deon George (3:633/509) for another term.


Jay
RC12

... The trouble with facts is that there are so many of them
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Northern Realms (1:12/0)

Re: Nomination
By: Jay Harris to All on Sat Feb 01 2025 10:34 pm

Howdy,

I would like to nominate Deon George (3:633/509) for another term.

Thanks Jay, I accept the nomination.


...ëîåï
--- SBBSecho 3.23-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hello All,

I would like to nominate Andrew Leary (1:320/219) for another term.

Best regards,
Niels
RC29

--- GoldED+/LNX 1.1.5-b20220504
* Origin: The Millennium BBS - fido.joncheere.be (2:29/0)

Hello Niels!

02 Feb 25 11:38, you wrote to all:

I would like to nominate Andrew Leary (1:320/219) for another term.

Thank you; I accept the nomination.

Andrew

--- GoldED+/LNX 1.1.5-b20240209
* Origin: From the Desk of the FTSC Administrator (1:320/219)

Hi,

I also would like to nominate Andrew Leary (1:320/219).

Greetings,
Rudi

--- D'Bridge 4
* Origin: Light Station (2:292/140)

Hello,

I'd like to nominate Tim Schattkowsky, 2:2/29

Thank you. :)

Ciao.
Fabio.
--- AfterShock/Android 1.6.6
* Origin: Mimac Rebirth Boss Mobile Point (2:335/364.3)

Hello everybody!

I hereby nominate Jason Bock (1:267/310) for a position as a Standing Member of the FTSC.

Thank you,

Andrew Leary
RC16

--- GoldED+/LNX 1.1.5-b20240209
* Origin: From the Desk of the New England Janitor (1:320/219)

On <08 Feb, 05:44>, Andrew Leary wrote to All :

Hello everybody!

I hereby nominate Jason Bock (1:267/310) for a position as a Standing Member
of the FTSC.

Thank you,

Andrew Leary
RC16

--- GoldED+/LNX 1.1.5-b20240209
* Origin: From the Desk of the New England Janitor (1:320/219)

Thank you for the nomination. I accept the nomination.

Thank you again,

Jason

--- ProBoard v2.32
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

Andrew wrote (2025-02-08):

Hello everybody!

I hereby nominate Jason Bock (1:267/310) for a position as a Standing Member of the FTSC.

Thank you,

Thanks but no thanks. He failed the basic competency test:

poll 1:267/310
$ -d 1:267/310@fidonet
+ 19:19 [6769] call to 1:267/310@fidonet
+ 19:19 [6769] outgoing session
- 19:19 [6769] SYS SiliconUnderground - ProBoard / FuNet WHQ
- 19:19 [6769] ZYZ Jason Bock
- 19:19 [6769] LOC Rochester, NY
- 19:19 [6769] NDL CM,IBN
- 19:19 [6769] TIME 2025/02/08 13:19:08 -5:00
- 19:19 [6769] VER Internet Rex 2.31 Win32 (binkp/1.1)
+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)
+ 19:19 [6769] addr: 1:1/101@fidonet.org (n/a or busy)
+ 19:19 [6769] addr: 1:267/311@fidonet.org (n/a or busy)
[....]
? 19:19 [6769] called 1:267/310@fidonet, but remote has no such AKA
+ 19:19 [6769] done (to 1:267/310@fidonet, failed, S/R: 0/0 (0/0 bytes))

But hey, at least you have just enough candidates for more years of nothing.

---
* Origin: No REPLY kludge - no reply (2:280/464.47)

Oli wrote to Andrew Leary <=-

I hereby nominate Jason Bock (1:267/310) for a position as a

Standing

Member of the FTSC.

Thank you,

Thanks but no thanks. He failed the basic competency test:

poll 1:267/310
$ -d 1:267/310@fidonet
+ 19:19 [6769] call to 1:267/310@fidonet
+ 19:19 [6769] outgoing session
- 19:19 [6769] SYS SiliconUnderground - ProBoard / FuNet WHQ
- 19:19 [6769] ZYZ Jason Bock
- 19:19 [6769] LOC Rochester, NY
- 19:19 [6769] NDL CM,IBN
- 19:19 [6769] TIME 2025/02/08 13:19:08 -5:00
- 19:19 [6769] VER Internet Rex 2.31 Win32 (binkp/1.1)
+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)
+ 19:19 [6769] addr: 1:1/101@fidonet.org (n/a or busy)
+ 19:19 [6769] addr: 1:267/311@fidonet.org (n/a or busy)
[....]
? 19:19 [6769] called 1:267/310@fidonet, but remote has no such AKA
+ 19:19 [6769] done (to 1:267/310@fidonet, failed, S/R: 0/0 (0/0 bytes))

But hey, at least you have just enough candidates for more years of nothing.

I have domain fido alias-for fidonet
domain fidorus alias-for fidonet
domain fido7 alias-for fidonet
domain fidonet.org alias-for fidonet domain fidonet.net alias-for fidonet i
in my binkd config file and this works. He is doing nothing wrong and in fact maybe more correct

Sean


... BBBS: https://binkd.rima.ie

--- BBBS/LiR v4.10 Toy-7
* Origin: There Can Only Be 1 (2:263/1)

Oli wrote to Andrew Leary <=-

I hereby nominate Jason Bock (1:267/310) for a position as a Standing Member of the FTSC.

Thanks but no thanks. He failed the basic competency test:

poll 1:267/310
$ -d 1:267/310@fidonet
+ 19:19 [6769] call to 1:267/310@fidonet
+ 19:19 [6769] outgoing session
- 19:19 [6769] SYS SiliconUnderground - ProBoard / FuNet WHQ
- 19:19 [6769] ZYZ Jason Bock
- 19:19 [6769] LOC Rochester, NY
- 19:19 [6769] NDL CM,IBN
- 19:19 [6769] TIME 2025/02/08 13:19:08 -5:00
- 19:19 [6769] VER Internet Rex 2.31 Win32 (binkp/1.1)
+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)
+ 19:19 [6769] addr: 1:1/101@fidonet.org (n/a or busy)
+ 19:19 [6769] addr: 1:267/311@fidonet.org (n/a or busy)
[....]
? 19:19 [6769] called 1:267/310@fidonet, but remote has no such AKA
+ 19:19 [6769] done (to 1:267/310@fidonet, failed, S/R: 0/0 (0/0
bytes))

Works for me:

BinkIT/2.41 invoked with options: -l 1:267/310
Attempting poll for node 1:267/310@fidonet
JSBinkP/4 callout to 1:267/310@fidonet started
Connecting to 1:267/310@fidonet at siliconu.com:24554
Peer version: Internet Rex 2.31 Win32
Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
Authentication successful:
/sbbs/exec/binkit.js executed in 2.00 seconds

Maybe it's you that is mis-configured.



... I'd love to help you out. Which way did you come in?
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

//Hello Fabio,//

on *05.02.25* at *18:01:49* You wrote in Area *FTSC_PUBLIC*
to *All* about *"Nomination"*.

Hello,

I'd like to nominate Tim Schattkowsky, 2:2/29

Thank you. I accept.

Regards,
Tim

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

Re: Re: Nomination
By: Sean Rima to Oli on Sat Feb 08 2025 07:29 pm

Howdy,

+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)

in my binkd config file and this works. He is doing nothing wrong and in fact maybe more correct

More correct?

http://ftsc.org/docs/frl-1028.002


...ëîåï
--- SBBSecho 3.23-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hello deon!

09 Feb 25 16:14, you wrote to Sean Rima:

+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)

in my binkd config file and this works. He is doing nothing wrong
and in fact maybe more correct

More correct?

http://ftsc.org/docs/frl-1028.002

You are correct that this document indicates the domain part of an FTN address cannot exceed 8 characters, or contain characters other than lowercase letters, digits, or the three "safe" characters (- _ ~). This would seem to preclude using the extensions, as the period/dot character (.) is not permitted.

However, this document was a FidoNet Standards Proposal that was not promoted and published as a FidoNet Technical Standard. It is preserved in the FTSC reference library for information purposes only. While it is recommended to comply with the requirements set forth in this document, it is NOT required.

BinkD itself has long had functionality to work around problems caused by nodes specifying domain names improperly.

Andrew

--- GoldED+/LNX 1.1.5-b20240209
* Origin: From the Desk of the FTSC Administrator (1:320/219)

deon wrote to Sean Rima <=-

Re: Re: Nomination
By: Sean Rima to Oli on Sat Feb 08 2025 07:29 pm

Howdy,

+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)

in my binkd config file and this works. He is doing nothing wrong and
in
fact maybe more correct

More correct?

http://ftsc.org/docs/frl-1028.002

As Andrew beat me to it, but this is not a standard.

Sean

... A woman drove me to drink, and I never had the courtesy to thank her.

--- BBBS/LiR v4.10 Toy-7
* Origin: TCOB1: https/binkd/telnet binkd.rima.ie (2:263/1)

Hi Sean,

+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)

in my binkd config file and this works. He is doing nothing wrong
and in fact maybe more correct

More correct?
http://ftsc.org/docs/frl-1028.002

As Andrew beat me to it, but this is not a standard.

It doesn't matter if it's a standard. The *FTN* domain for FidoNet is "fidonet". There is no more correct or less correct way. It's binary. You use the correct FTN domain or don't.

Even binkd.cfg explains it:

# Aliases to support known *DNS* domain zones
# (some people mix up the terms "FTN domain" and "DNS internet domain")
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet


* Origin: kakistocracy (2:280/464.47)

On <09 Feb, 10:40>, Sean Rima wrote to deon :

deon wrote to Sean Rima <=-

Re: Re: Nomination
By: Sean Rima to Oli on Sat Feb 08 2025 07:29 pm

Howdy,

+ 19:19 [6769] addr: 1:267/310@fidonet.org (n/a or busy)

in my binkd config file and this works. He is doing nothing wrong and
in
fact maybe more correct

More correct?

http://ftsc.org/docs/frl-1028.002

As Andrew beat me to it, but this is not a standard.

Sean

... A woman drove me to drink, and I never had the courtesy to thank her.

--- BBBS/LiR v4.10 Toy-7
* Origin: TCOB1: https/binkd/telnet binkd.rima.ie (2:263/1)

Hello,

I changed the domain to make it align with values and morals.

Thank you,

Jason Bock

--- ProBoard v2.32
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

Hello Jason,

On Sunday February 09 2025 11:23, you wrote to Sean Rima:

@PID: ProBoard 2.32 J
@TID: FastEcho 1.46 43281
On <09 Feb, 10:40>, Sean Rima wrote to deon :

No MSGID
No REPLY
No TZUTC
No CHRS

I changed the domain to make it align with values and morals.

Thank you.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nieuw Schnøørd (2:280/5555)

Re: Nomination
By: Andrew Leary to deon on Sun Feb 09 2025 01:10 am

Howdy,

BinkD itself has long had functionality to work around problems caused by nodes specifying domain names improperly.

And hence why I thought the original comment "more correct", isnt really "more correct".


...ëîåï
--- SBBSecho 3.23-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

MvdV> Hello Jason,
MvdV>
MvdV> On Sunday February 09 2025 11:23, you wrote to Sean Rima:
MvdV>
MvdV> JB> @PID: ProBoard 2.32 J
MvdV> JB> @TID: FastEcho 1.46 43281
MvdV> JB> On <09 Feb, 10:40>, Sean Rima wrote to deon :
MvdV>
MvdV> No MSGID
MvdV> No REPLY
MvdV> No TZUTC
MvdV> No CHRS
MvdV>
The software is rom the 90's. I am actually working on updating the message system with the correct standards. ;)

--- ProBoard v2.32
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

Jason,

MvdV> No MSGID
MvdV> No REPLY
MvdV> No TZUTC
MvdV> No CHRS

The software is rom the 90's. I am actually working on updating the message system with the correct standards. ;)

One man's standard is another man's error.

Are all these covered by standards?

\%/@rd

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

Hej Ward!

One man's standard is another man's error.

Are all these covered by standards?

Two of them are covered by corrupted standards; the TZUTC and the CHRS kludges. The TZUTC kludge would require very little to make it compatible with timezone offsets while the CHRS kludge is almost totally a joke as far as standards go.

Het leven is goed,
Maurice

-o o- o- o-
(\ /) /) /)
^^ ^^ ^^ ^^
... Sterk zoals Bull, Smart Like Tractor.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Jason,

MvdV> No MSGID
MvdV> No REPLY
MvdV> No TZUTC
MvdV> No CHRS

The software is rom the 90's. I am actually working on updating the message system with the correct standards. ;)

One man's standard is another man's error.

Are all these covered by standards?

\%/@rd

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

Ward,

I do not think ProBoard followed any standards as there are a ton of proprietary libraries to work around different tasks. IT is somewhat clean code until you get into the libraries.

I am working on it. ;)

-Jason

--- ProBoard v2.32
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

09 Feb 2025 23:20, you wrote to Michiel van der Vlist:

MvdV>> No MSGID
MvdV>> No REPLY
MvdV>> No TZUTC
MvdV>> No CHRS
MvdV>>

The software is rom the 90's. I am actually working on updating the message system with the correct standards. ;)

Nice. Good luck! ;-)

I suggest you start with supporting MSGID/REPLY (FTS-0009), as they are the most important kludges, and leave the others for later.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

09 Feb 2025 23:20, you wrote to Michiel van der Vlist:

MvdV>> No MSGID
MvdV>> No REPLY
MvdV>> No TZUTC
MvdV>> No CHRS
MvdV>>

The software is rom the 90's. I am actually working on updating the message system with the correct standards. ;)

Nice. Good luck! ;-)

I suggest you start with supporting MSGID/REPLY (FTS-0009), as they are the most important kludges, and leave the others for later.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Carlos,

I agree.

Thank you,

Jason

--- ProBoard v2.32
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

Hello Ward!

10 Feb 25 21:23, you wrote to Jason Bock:

MvdV> No MSGID
MvdV> No REPLY
MvdV> No TZUTC
MvdV> No CHRS

The software is rom the 90's. I am actually working on updating
the message system with the correct standards. ;)

One man's standard is another man's error.

Are all these covered by standards?

MSGID and REPLY are defined in FTS-9 (http://ftsc.org/docs/fts-0009.001)
TZUTC is defined in FTS-4008 (http://ftsc.org/docs/fts-4008.002)
CHRS is defined in FTS-5003 (http://ftsc.org/docs/fts-5003.001)

So yes, all of the mentioned control paragraphs are covered by published FidoNet Technical Standards.

Andrew

--- GoldED+/LNX 1.1.5-b20240209
* Origin: From the Desk of the FTSC Administrator (1:320/219)

Hello Maurice!

10 Feb 25 21:20, you wrote to Ward Dossche:

Two of them are covered by corrupted standards; the TZUTC and the CHRS kludges. The TZUTC kludge would require very little to make it
compatible with timezone offsets while the CHRS kludge is almost
totally a joke as far as standards go.

Keep in mind that FidoNet Technical Standards cover current practice in FidoNet. The FTSC does not have the power to revise standards and compel software authors to comply with such revisions. In many cases, software used in FidoNet is abandoned by its authors, source code is lost, or other circumstances that preclude changes being made.

Regards,

Andrew

--- GoldED+/LNX 1.1.5-b20240209
* Origin: From the Desk of the FTSC Administrator (1:320/219)

Hey Andrew!

Keep in mind that FidoNet Technical Standards cover current
practice in FidoNet.

No they don't. The current usage of the packed MSG format is not reflected by any currently published standard. It hasn't for decades now.

Life is good,
Maurice

-o o- o- o- o- o- o- o- -o o- -o o- o- -o -o -o
(\ /) /) /) /) /) /) /) (\ /) (\ /) /) (\ (\ (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - Sweet Sixteen Penguins of the Apocalypse.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)