TZUTC: 1100   
   MSGID: 763.fdn_ipv6@3:633/509 23e78fc2   
   REPLY: 2:203/2 5f820762   
   PID: Synchronet 3.18c-Linux  Oct  9 2020 GCC 8.3.0   
   TID: SBBSecho 3.11-Linux r3.179 Oct  9 2020 GCC 8.3.0   
   CHRS: ASCII 1   
   NOTE: SlyEdit 1.73 (2020-03-31) (ICE style)   
     Re: New one   
     By: Björn Felten to Deon George on Sat Oct 10 2020 09:11 pm   
      
    DG>> That's funny :)   
    BF>    How so?   
      
   Rules of the ipv6 f1d0 game:   
   * Zone must be between 1-9999 - no problem there, if this network has   
   scalability issues, its unlikely to be in our lifetime.   
   * Net must be between 1-9999 - note to ZC's dont create nets > 9999 otherwise   
   if they represent their IPv6 address using the unofficial f1d0 convention, it   
   will be confusing.   
   * Node must be between 1-9999 - note to NC's - see above. Sorry Sergey, you   
   must get a new node number if you want to play.   
      
   Sorry, I'm taking the piss, no disrespect, and text messages dont show the   
   giggles I'm having because I've represented my nodename in hex prefixed f1d0   
   that generated this thread. And I'm not sure that anybody would ever look at   
   it, or if they did, that it would answer a question by doing so.   
      
   It just seems logical to me, that if you wanted to have a f1d0 convention, you   
   would choose hex, since numbers that are used to represent a node can be   
   between 0-32767, and that can be represented completely in a IPv6 address if   
   somebody chose to do so.   
      
   So, I'm guessing I cant have the little "f" next to my listing? :(   
      
   ...ëîåï   
      
   ... It works better if you plug it in.   
   --- SBBSecho 3.11-Linux   
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)   
   SEEN-BY: 1/123 90/1 120/340 123/131 226/30 227/702 229/424 426 550   
   SEEN-BY: 229/664 1016 240/5832 249/206 317 400 317/3 322/757 342/200   
   SEEN-BY: 633/0 267 280 281 410 412 509 640/1384 712/848   
   PATH: 633/509 280 229/426