TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 216bf7f7   
   REPLY: 1621.fdn_binkd@3:633/509 264cb5ec   
   TZUTC: -0500   
    de> is not), but that is moot - if your software doesnt work with it, I dont   
    de> get why you wouldnt want to make it work with it, even if the binkd   
    de> development team werent interested in "fixing" it the way you want it   
    de> "fixed".   
      
   My software works fine with it, there is nothing I could possibly change.  It   
   handles all formats of escaping and its configurable per node.  The person in   
   this case is using a version many years old with a bug, but you knew that.   
      
   You know it because I have explained this to you now in three different   
   messages, and you keep ignoring it.  I don't want anything fixed.  I never   
   posted here asking for anything, someone else did.  I could care less if BINKD   
   adds it or not but given its a FTS guideline I think it should.  I keep   
   telling you that but again, you just ignore it.   
      
   You should ask yourself the same question you just asked me:   If implementing   
   the *FTS recommendations for handling filename escaping* into BINKD would make   
   it work better with more mailers, then why not do it?  Wouldn't you want to   
   make it better?  BINKD will fail with any legacy mailer that uses the \XX   
   format and those legacy mailers cannot be updated only BINKD can.   
      
   To answer your "would you want to fix it" question.  When this issue was   
   brought to me back in 2020 I made changes within an hour of reporting it, and   
   the person who did so didn't have to push through all this drama and   
   resistance for no reason.  So yes, as my reputation fully has proven over more   
   than two decades, I respond very quickly and fix issues often times in the   
   same day its reported.  You can go back 20 years and see this very thing   
   happen over and over again.   
      
   Its really weird how you guys go on and on about FTS compliance and then you   
   ignore whats going on and cherry pick what should and shouldn't be applied   
   when it aligns with whatever narrative you're trying to push.   
      
   ... Message encrypted: Press ALT-F4 to read encoded message   
   --- Mystic BBS v1.12 A48 2022/01/14 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 14/0 15/0 30/0 80/1 90/1 103/705 105/81 106/201 114/709   
   SEEN-BY: 120/340 616 123/10 131 129/215 305 153/7715 154/10 30 40   
   SEEN-BY: 154/50 700 203/0 218/700 220/80 90 221/1 6 226/18 30 227/114   
   SEEN-BY: 227/201 229/110 200 307 310 317 424 426 550 664 700 240/1120   
   SEEN-BY: 240/5832 249/206 266/512 280/464 5555 282/464 1038 292/854   
   SEEN-BY: 301/0 1 101 113 123 812 317/3 320/219 322/757 335/364 341/66   
   SEEN-BY: 342/200 396/45 460/58 633/280 712/848 920/1 2320/105 3634/12   
   SEEN-BY: 5020/1042 5058/104   
   PATH: 129/215 154/10 301/1 229/426