Groups.io: Changelog

Subscribe via RSS


May 8, 2020

  • NEW: When a person is banned from Groups.io, we now log that in all groups they were a member of, and we remove all subscription data instead of just hiding it, which should keep sub counts correct.
  • BUGFIX: The sending of a new confirmation email by a moderator using the 'Send Confirmation Email' button was not logged properly in the email delivery section.
  • NEW: Logging to the activity log when we send the group guidelines out and when we send monthly reminder messages out.
  • INTERNAL: Optimized a database call when generating digests.
  • BUGFIX: Don't include links to profiles of banned members when viewing messages.
  • CHANGE: When visiting a manual in the help center, display the table of contents.
  • CHANGE: Wiki pages now use the wiki page ID instead of the title (with exceptions for _Sidebar/_Footer) to prevent link breakage when titles change.
  • INTERNAL: A lot of work to enable distributed tracing of the internal systems.

May 1, 2020

  • NEW: Updated Help Center manuals with Nina's updates, including reformatted PDFs.
  • SYSADMIN: Continued debugging issues with the new database server.
  • CHANGE: Documented photo/file upload size limits and increased them for premium/enterprise groups.
  • SYSADMIN: Upgraded the web servers with more memory to deal with increased file/photo upload sizes.
  • CHANGE: Rolled back the List-Id change from 4/25/20.
  • BUGFIX: Sorting by file type in the Files section would sometimes return the same results over multiple pages because our sort criteria wasn't stable.
  • INTERNAL: We now clean up unused RSS feeds in the database.
  • INTERNAL: On an edited message, check if the digest message exists already before adding it, to prevent postgres log messages.
  • INTERNAL: Changed nginx log format back to combined to goaccess can parse user agents.
  • INTERNAL: Work to make it easier to add additional FBL providers.
  • API: /getevent wasn't obeying the group calendar permissions setting.
  • NEW: We now parse more information about which message was flagged as spam from an FBL report, and send that out to the user and group owners.