TZUTC: -0800   
   MSGID: 54136.syncprog@1:103/705 2dcd3e3d   
   PID: Synchronet 3.21b-Linux master/177a369d2 Jan 04 2026 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/f717faea9 Jan 12 2026 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/6efa906bdaa162ea1eb95d6a   
   Modified Files:   
   	src/sbbs3/answer.cpp bat_xfer.cpp chat.cpp data.cpp email.cpp exec.cpp   
   execfunc.cpp getnode.cpp listfile.cpp load_cfg.c logon.cpp logout.cpp main.cpp   
   newuser.cpp readmail.cpp readmsgs.cpp sbbs.h scandirs.cpp scansubs.cpp   
   src/sbbs3/scfg/scfgsys.c src/sbbs3/scfgdefs.h scfglib1.c scfgsave.c str.cpp   
   text_sec.cpp tmp_xfer.cpp useredit.cpp writemsg.cpp xtrn_sec.cpp   
   Log Message:   
   Support multiple loadable modules per module type, restricted via ARS   
      
   Implemented this idea discussed between Nightfox and myself:   
      
    RS> A configurable ARS for some loadable would be a good idea and allow a   
    RS> sysop to use built-in functions for some users and loadable modules for   
    RS> others.   
      
   One thing I've thought would be handy would be to have a user preference option   
   for that as well.  For instance, if a sysop has msglist or DDMsgReader set up   
   for the loadable module to list/read messages, it may be useful to have a   
   toggle option in the user preferences so users can specify whether they want to   
   use that or the stock Synchronet reader/lister.   
      
   ----   
      
   So with user properties exposed to ARS and loadable modules restricted via   
   ARS, it's now possible for a "toggle option" in (some yet to be written) user   
   preferences mod to toggle between (or at least "opt-out" from) loadable modules   
   (and possibly revert built-in functionality, when it's there).   
      
   Some of the "built-ins" (e.g. the batch transfer menu and file transfer menu)   
   are likely to get removed soon, so reverting to "built-in" doesn't make sense   
   in that case but you could at least limit what users (or user terminals) have   
   access to what loadable modules now. e.g. I plan to make the default/stock   
   configuration use msglist.js only for "ANSI AND COLS 80" users.   
      
   This includes recursion protection (refuses to execute recursively and logs   
   an error if attempted) for all loadable modules.   
      
   The SCFG configuration for Loadable Modules could use a little more love now   
   (help screens and such).   
   --- SBBSecho 3.34-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/705 105/81 106/201 124/5016 128/187 129/14   
   SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 700 810 226/30 227/114   
   SEEN-BY: 229/110 134 206 317 400 426 428 470 700 705 266/512 280/464   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426