TZUTC: -0700   
   MSGID: 56293.sync_sys@1:103/705 2b45701b   
   PID: Synchronet 3.20a-Linux master/e93b6dfa6 Aug 22 202 GCC 12.2.0   
   TID: SBBSecho 3.20-Linux master/984c371ae Sep 06 2024 20:48 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/issues/782#note_5598   
      
   > I was curious why the conditional call fixed things for you in   
   `randomString` but not for me, and after investigating it looks like it   
   didn't, at least not fully.   
      
   That's interesting - I guess it solved the immediate problem for the sysop and   
   appeared fixed, even if the string wasn't what I intended to generate.   
      
   > `randomString` could be refactored to use `ascii` as well.   
      
   I'll definitely keep this in mind especially if I go poking around in webv4   
   again.   
      
   The problem now is ... how many scripts in our codebase have similar   
   "problems", and do we need to use similar tricks going forward in new ones?   
   It'd be great if a fix of the underlying problem were possible, but that's   
   hard to say. I'll have to see what kind of RPi stuff I have kicking around   
   here and do some tinkering soon.   
   --- SBBSecho 3.20-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 90/1 102/401 103/1 17 705 105/81 106/201 124/5016   
   SEEN-BY: 153/7715 214/22 218/0 1 215 601 700 720 840 860 870 880 930   
   SEEN-BY: 226/30 227/114 229/110 114 206 317 400 426 428 470 550 700   
   SEEN-BY: 229/705 266/512 280/464 282/1038 291/111 301/1 320/219 322/757   
   SEEN-BY: 342/200 396/45 460/58 633/280 712/848 5075/35   
   PATH: 103/705 218/700 229/426