TZUTC: 0000   
   MSGID: 91.fido-doorgame@1:103/1 2d9caa5f   
   REPLY: 842.f_doors@1:2320/105 2d9c15ba   
   PID: Synchronet 3.21a-FreeBSD master/2e46e129c Dec 07 2025 Clang 19.1.7   
   TID: SBBSecho 3.32-FreeBSD master/2e46e129c Dec 07 2025 Clang 19.1.7   
   BBSID: BBSDEV   
   CHRS: ASCII 1   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: Re: Kannons and Katapults   
     By: Mike Powell to Stephen Hurd on Mon Dec 08 2025 09:10 am   
      
    > I am a little leary to blame "old software" when the software itself has no   
    > issue interpreting the tap of the enter key as "one" return... CR or LF or   
    > whatever.   It seems more like a case of syncterm, etc., sending an extra   
    > character when in telnet mode that older software -- i.e. most BBS software   
    > that isn't Synchronet or Mystic -- doesn't know what to do with.   
      
   That's exactly what it is, but doing that is *required* by the telnet protocol   
   under certain circumstances.   
      
    > That might be semantics but I it is odd that using an older terminal program   
    > over a telnet connection (with something like VMODEM) doesn't cause this,   
    > which makes me suspect it is the modern BBS terminal programs that have   
    > changed something.  I am sure the answer is "cause telnet protocol" but   
    > since we are using these terminal programs to telnet into BBSes and not old   
    > VAX   
    > or mainframe machines, I have to wonder who thought that was necessary.   
      
   It's actually the other way around... the old things like VModem handled the   
   telnet protocol and the door game didn't have to worry about it.  Many modern   
   doors however are being passed the socket itself and now the door needs to   
   support the telnet protocol and every doorkit author needs to understand the   
   telnet protocol instead of it being handled by the VModem and only the person   
   who is setting out to write a telnet package needs to deal with the telnet   
   protocol.   
      
   Having the door "speak" telnet when it is passed a socket also ends up causing   
   issues when the BBS uses SSH instead of telnet because SSH is an 8-bit-clean   
   protocol, so all of the telnet things that a door has to do, it has to not do   
   for SSH.   
      
   Basically it's "cause door is being passed a raw socket and has to telnet   
   protocol itself" instead of the much more sane "telnet server does telnet,   
   door doesn't care".   
   --- SBBSecho 3.32-FreeBSD   
    * Origin: BBSDev.net - The BBS Developers Network (1:103/1)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 305 153/7715 154/110 218/0 1 109 215 601 700 810 840   
   SEEN-BY: 218/860 880 900 226/30 227/114 229/110 112 134 200 206 307   
   SEEN-BY: 229/317 400 426 428 470 664 700 705 266/512 291/111 301/1   
   SEEN-BY: 320/219 322/757 342/200 396/45 633/280 712/848 902/26 5020/400   
   SEEN-BY: 5075/35   
   PATH: 103/1 218/700 229/426