REPLY: 2:280/464 60786404   
   MSGID: 1:153/7001 60787126   
   CHRS: UTF-8 4   
   -={ 2021-04-15 17:00:22.008942453+00:00 }=-   
      
   Hey Wilfred!   
      
    WvV> To review if they still describe current practice,   
      
   Which is?   
      
    WvV> or could be worded better, not to change them to something   
    WvV> incompatible with current practice. ;)   
      
   Nope.  Speaking as a nodelisted sysop, as well as the only user of an official   
   point system, and especially as a standing member of the FTSC I refuse to   
   subscribe to mob rule which is where 'current practice' usually leads.  On   
   this particular subject of the MSGID/REPLY kludges my gut feeling is to leave   
   the wording as is since it leaves open a door for improvement if and when it   
   presents itself.  I think it is clear enough without any alterations, up to   
   and including my suggestion for a new and improved flexible hex character   
   representation of unixtime.   
      
   I look forward to the review of this particular document.  I have much to say   
   about it especially about the misuse of the MSGID to introduce proprietary   
   addressing.  That has to go no matter what harm it might bring to the software   
   in question.   
      
   Life is good,   
   Maurice   
      
   ... Leorna hwæthwugu æt ðam wisran, þæt þu mæge læran þone unwisran.   
       Learn something from the wise, so you can teach the ignorant.   
   --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)   
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)   
   SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 129/305 153/105   
   SEEN-BY: 153/135 757 802 7001 226/30 227/114 229/101 424 426 452 664   
   SEEN-BY: 229/700 1016 1017 240/5832 249/206 317 400 261/38 282/1038   
   SEEN-BY: 301/1 317/3 322/757 342/17 200 633/280   
   PATH: 153/7001 757 229/664 426