1. 04 Dec, 2015 1 commit
  2. 26 Nov, 2015 2 commits
  3. 20 Sep, 2015 1 commit
  4. 05 May, 2015 1 commit
  5. 27 Apr, 2015 1 commit
    • rswindell's avatar
      Enhancement at the request of Nightfox: · d57c3830
      rswindell authored
      Optionally, external modules may be executed in place of "built-in" operations
      for:
      - reading mail (email or netmail)
      - scanning posts (searching/scanning/reading a single sub-board)
      - scanning sub-boards (all, one, or a group)
      
      Each of these may be configured (in SCFG->System->Loadable Modules)
      with command-line options for a total length of up to 63 characters.
      
      Note to module programmers: each module here will be passed additional
      command-line arguments to indicate how or why the user operation was invoked.
      
      For the Reading Mail module, the 'which' value (in decimal) and the user-number
      is passed (in decimal). Usually the user-number will be the current user logged
      in, but not always (e.g. if the user is a sysop and reading other user's mail).
      The 'which' values (defined in load/sbbsdefs.js) of MAIL_YOUR, MAIL_SENT,
      and MAIL_ALL must be handled (MAIL_ANY won't be used).
      
      For the Scan Posts module, the sub-board number and scan mode (both in decimal)
      and the 'find' string (text being searched for) are passed as arguments
      (in that order). The scan mode values (defined in sbbsdefs.js) are the same as
      those supported by bbs.scan_posts(). All of the values should be supported
      and they can be combined (e.g. SCAN_CONST|SCAN_NEW
      and SCAN_NEW|SCAN_TOYOU). The 'find' string is only used if the SCAN_FIND mode
      bit is set. It is the responsibilty of the module (if configured) to enforce
      sub-board read access restrictions.
      
      For the Scan Subs module, the first argument is 1 if "all subs" are being
      scanned, 0 otherwise (normally the user is prompted for the breadth of the
      scan in this case, but that's up to the module author), and the scan 'mode' is
      passed in decimal, in that order. If the SCAN_FIND mode flag is passed in, this
      module should prompt the user for the text string to search for. If this module
      is not configured, the Scan Posts module will be executed for each sub-board
      scanned.
      
      Recursion protection was added, so it is actually possible for the Read Mail
      module, for example, to call bbs.read_mail() and it'll work, but why would you?
      
      If any of these user operations are initiated during logon, at the request of
      Baja or JavaScript module, or whatever, and if the module is actually
      configured (and not already executing to handle the operation), the module
      will be executed in-place-of the built-in functionality. Feedback welcome,
      d57c3830
  6. 12 May, 2013 1 commit
  7. 13 Feb, 2013 2 commits
  8. 06 Jan, 2013 1 commit
  9. 24 Oct, 2012 1 commit
  10. 03 Sep, 2011 1 commit
  11. 25 Aug, 2011 1 commit
  12. 21 Jul, 2011 1 commit
    • rswindell's avatar
      Enhancement: most question-type text.dat entries are now optional. · 77a2cda0
      rswindell authored
      That is, if any of the following text.dat entries are set to a blank/emtpy
      string (by editing ctrl/text.dat or via run-time script modification), the
      question will not be asked of the user allowing greater sysop-customization
      of hard-coded processes (e.g. new user application):
      ClearUploadQueueQ
      ClearDownloadQueueQ
      HangUpAfterXferQ
      ChatWithGuruInsteadQ
      ForwardMailQ
      DownloadBatchQ
      LogOffQ
      DeleteErrorLogQ
      ClearErrCounter
      DeleteGuruLogQ
      AutoTerminalQ
      AnsiTerminalQ
      ColorTerminalQ
      ExAsciiTerminalQ
      CallingFromNorthAmericaQ
      ReadYourMailNowQ
      NScanAllGrpsQ
      SScanAllGrpsQ
      NewPasswordQ
      ContinueQ
      EnterYourPhoneNumber
      UserInfoCorrectQ
      UseExternalEditorQ
      DownloadAttachedFileQ
      AddSubToNewScanQ (new)
      RemoveFromNewScanQ
      DisplaySubjectsOnlyQ
      Post
      SearchExtendedQ
      ViewSysInfoFileQ
      ViewLogonMsgQ
      WithLineNumbersQ
      77a2cda0
  13. 10 Mar, 2010 1 commit
  14. 06 Mar, 2010 1 commit
  15. 18 Oct, 2009 1 commit
    • rswindell's avatar
      Don't allow replies to messages with the "NoReply" attribute set. · 5aadeb4d
      rswindell authored
      Don't prompt for "delete mail from everyone" when there is only one e-mail
      waiting for the user.
      Use some existing text.dat entries (some old and some recently added) where
      identical static strings were still being used for no apparent reason.
      Added several text.dat entries for the QWK settings menu, node status, and
      some other single-line messages (replacing static strings).
      5aadeb4d
  16. 28 Jun, 2009 1 commit
  17. 20 Mar, 2009 3 commits
    • rswindell's avatar
      6b8a5be3
    • rswindell's avatar
      More local logon kruft removal. · 15442b2f
      rswindell authored
      15442b2f
    • rswindell's avatar
      ARS improvements: · 1cdf2c10
      rswindell authored
      Added HOST and IP keywords to allow restricted access/privileges to/for
      specific remote hostnames or IP addresses (wildcards allowed).
      All string-argument type ARS keywords (e.g. SHELL, PROT, etc.) now support .can
      style wildcards.
      The current remote client is now used for protocol, host, and IP ARS checking,
      when available, so this requires passing the client pointer around (which
      explains why so many files are touched by this change) and takes care of a
      long standing to-do item (the user's 'modem' value was used for the PROT
      value checking, which was not always correct).
      1cdf2c10
  18. 21 Feb, 2009 1 commit
  19. 15 Feb, 2009 1 commit
  20. 25 Feb, 2008 1 commit
  21. 15 Feb, 2008 1 commit
  22. 23 Aug, 2007 1 commit
  23. 14 Aug, 2007 1 commit
  24. 13 Aug, 2007 1 commit
  25. 02 Nov, 2006 1 commit
  26. 30 Sep, 2005 1 commit
  27. 20 Sep, 2005 1 commit
  28. 12 Aug, 2005 2 commits
  29. 05 Jan, 2005 1 commit
  30. 22 Nov, 2004 2 commits
  31. 27 Oct, 2004 1 commit
  32. 21 Oct, 2004 1 commit
  33. 08 Sep, 2004 1 commit
  34. 30 May, 2004 1 commit