TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 8f1b38f1   
   REPLY: 2:201/137 d8057952   
   TZUTC: -0400   
    BW>  BW> * FTP uploads appear to corrupt the file base. If I scroll down the   
    BW>    
    BW> This is still a problem; as soon as I FTP upload a file to a file base   
    BW> that already has a file, it appears to corrupt the file base. This time   
      
   This turned out to be Linux-specific so I had to set up some tests there.  The   
   7/11 release should fix this.   
      
    BW>  BW> * For a normal account (not a QWK account), when selecting the messag   
    BW>  BW> bases   to scan from the message menu, i.e. (MZ) Toggle new scan base   
    BW>  BW> with an empty   Data field, Mystic appears to be selecting the wrong   
    BW>  BW> message base when I   enter a number:   
    BW>    
    BW> That one is still there. Now it appears to be selecting a message base   
    BW> in some other message group? Not sure, because I can't see any changes   
      
   Yeah this was a freak accident.  Turns out when I was editing something else I   
   accidentally hit a key and it was passing a bad default value to a function   
   (-10 instead of -1).   
      
   I think now that I changed it back to -1 we should be okay in the 7/11 build   
   but let me know once you have a chance to try it!   
      
    BW> Also, a few more things (I do not know if all have been present earlier)   
    BW> and suggestions:   
    BW>    
    BW> * 5mooth-mist25.ans is present in the text directory of the default   
    BW> theme. Should it be there? Perhaps for some gallery function or similar?   
      
   Yes its used as the ANSI in the Demos menu for File Viewer.   
      
    BW> * When editing user flags in the user editor, ANSI escape codes   
    BW> (e.g. arrow up yields a "P") toggle the corresponding flags. Would it be   
    BW> possible for Mystic to "filter out" anything with an escape before it?   
      
   This isn't in the 7/11 update but should be fixed in the next build.   
      
    BW> * When selecting a function/command in the menu editor, -R is listed   
    BW> after -S.   
      
   Fixed.   
      
    BW> * After uploading a file via FTP, the FTP command processor will   
    BW> become unresponsive until upload testing has finished (if one has enabled   
    BW> upload testing). Could Mystic send e.g. a "452 Requested action not   
    BW> taken. Still testing uploaded file. Please wait a little and try again."   
      
   Not for now.  It may be possible to send some status codes to like the client   
   know its being tested and when to resume but I would need to test that with   
   various clients.   
      
   Ideally it would spawn a thread for testing but there needs to be a thread   
   queue and a limit to it otherwise a bad actor could use it as a form of DDOS   
   attack.  This is something I want to do but its a chunk of work and probably a   
   low priority given how few people will actually use this feature.   
      
   I think short term is to experiment with status messages and long term is to   
   implement a testing thread/queue.   
      
   ... The dog ate my .REP packet   
      
   --- Mystic BBS v1.12 A48 2022/07/07 (Windows/32)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10   
   SEEN-BY: 123/120 131 129/215 305 330 331 153/7715 154/10 30 40 50   
   SEEN-BY: 154/700 218/700 840 220/70 90 221/6 226/17 18 30 100 227/114   
   SEEN-BY: 227/201 229/110 111 112 113 206 307 310 317 400 424 426 428   
   SEEN-BY: 229/452 470 550 664 700 250/5 8 266/512 267/800 280/464 282/1038   
   SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12   
   PATH: 129/215 154/10 770/1 317/3 229/426