Skip to content
Snippets Groups Projects
  1. Jun 09, 2021
  2. Jun 08, 2021
  3. May 31, 2021
  4. May 30, 2021
  5. Mar 08, 2021
  6. Mar 07, 2021
  7. Dec 22, 2020
    • Rob Swindell's avatar
      Remove dynamic HTML index support from FTP server · 22e8d2e3
      Rob Swindell authored
      The days of browsers rendering HTML served-up via FTP are over, so remove this feature. This also removes all JavaScript support from the FTP server and that is a bit odd as it was one of the first Synchronet components for which I added JS support.
      
      Removing this feature was pretty painless; much easier than adding it was. The main motivation was less cruft to port to the file base in the works. There should be no more references to 00index.html anywhere at this point. Bye bye cool feature, we'll miss you.
      22e8d2e3
  8. Sep 21, 2020
  9. Sep 14, 2020
  10. Sep 07, 2020
  11. Aug 16, 2020
  12. Aug 15, 2020
  13. Aug 13, 2020
  14. Jul 20, 2020
  15. May 06, 2020
  16. May 03, 2020
  17. Apr 28, 2020
  18. Apr 13, 2020
  19. Feb 10, 2020
  20. Jan 08, 2020
  21. Oct 05, 2019
    • Rob Swindell's avatar
      Don't allow replying to one's self · b3e9a28a
      Rob Swindell authored
      When posting a reply-message, if the original "from" field is the
      current user's alias, then reply to the original message's "to"
      value instead of the "from" value. This is also how sbbs handles
      reply 'to' fields.
      b3e9a28a
  22. Sep 24, 2019
    • Rob Swindell's avatar
      It was observed that httpSess threads would consume ~15% of a CPU · 2fbe160d
      Rob Swindell authored
      Using Linux top, long-running (hundreds of hours) httpSess threads were seen
      consuming ~15% of a CPU core. This loop calls time() and yield() in a tight
      loop, so instead mswait(50) (milliseconds), which reduces the CPU utilization
      considerable (down to < 1%), but will slightly impact the frequency with
      which the events callbacks are invoked. A better scheme would be to block
      while waiting for an event or a timeout (e.g. 1 second), so this is not a
      great solution. More of a work-around.
      2fbe160d
  23. Sep 18, 2019
    • Rob Swindell's avatar
      Convert non-UTF-8 message header fields (to/from) to UTF-8 · 6a703516
      Rob Swindell authored
      Some messages come from non-English locales with non-UTF-8 charsets
      (e.g. CP437), so their to/from fields may contain non-ASCII/non-UTF-8
      characters (e.g. "Björn Felte") - so convert these fields (to/from)
      to UTF-8, as needed. Uses the new(ish) utf8_encode() function, so you
      must have a recent v3.17c build.
      I did not transcode message subjects as I'm not clear how they are stored
      and copied here. That's probably something better handled by echicken.
      6a703516
  24. Sep 16, 2019
  25. Sep 06, 2019
  26. Sep 05, 2019
  27. Aug 30, 2019
  28. Aug 27, 2019
  29. Aug 26, 2019
    • Rob Swindell's avatar
      UTF-8 encode user signatures and mark msg headers as UTF-8 encoded · 7fb69813
      Rob Swindell authored
      When run with a build that includes utf8_encode() (new global JS
      function), use it to convert the user's .sig file from CP437 to UTF-8.
      
      When creating a new message (post or email), set the auxattr flag
      MSG_HFIELDS_UTF8 since we support UTF-8 chars (not CP437) in message
      header fields (e.g. to/from/subject). Requires updated load/smbdefs.js
      7fb69813
  30. Aug 24, 2019
  31. Aug 23, 2019
Loading