Subj : f1d0
To   : Deon George
From : Michiel van der Vlist
Date : Sun Oct 11 2020 13:33:34

Hello Deon,

On Sunday October 11 2020 11:50, you wrote to Bj”rn Felten:
                                                ^
 DG> @MSGID: 763.fdn_ipv6@3:633/509 23e78fc2
 DG> @REPLY: 2:203/2 5f820762
 DG> @PID: Synchronet 3.18c-Linux  Oct  9 2020 GCC 8.3.0
 DG> @TZUTC: 1100
 DG> @TID: SBBSecho 3.11-Linux r3.179 Oct  9 2020 GCC 8.3.0
 DG> @CHRS: ASCII 1
            ^^^^^^^
 DG>   By: Björn Felten to Deon George on Sat Oct 10 2020 09:11 pm
             ^
CHRS kludge doesn't match character encoding in use....

 DG> It just seems logical to me, that if you wanted to have a f1d0
 DG> convention, you would choose hex, since numbers that are used to
 DG> represent a node can be between 0-32767, and that can be represented
 DG> completely in a IPv6 address if somebody chose to do so.

I must admit that from the techie POV there is some logic to this line of reasoning.

As ever so often in life however, that is not how this evolved. The one that started it - it wasn't me - apparently thought it was a good idea to present the node number in human readable, and human easy to remember, form. iow in the from that node numbers are usually presented to humans: in decimal.

So far 29 others have followed this idea.

 DG> So, I'm guessing I cant have the little "f" next to my listing? :(

Sorry, no. Decimal is the game.

If you do not like the rules you are free to start your own game of course. But if you do, please be so kind to use something other than "f1d0" for the first 16 bits of the host part of the address. "f1d0" is already in use as a keyword for representing the node number in decimal.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: he.net certified sage (2:280/5555)

.