Groups.io: Changelog

Subscribe via RSS


March 13, 2020

  • API: Added email_address field to group object.
  • BUGFIX: There was a bug with event RSVPs which could prevent some people from RSVPing to an event.
  • BUGFIX: Removed duplicate Member Sync buttons from various settings pages. This had been renamed to Service Sync and placed elsewhere.
  • API: Fixed sort for /getmembernotices endpoint.
  • CHANGE: Separate the settings in the Default Sub Settings page into two panels for greater clarity.
  • CHANGE: For moderator only hashtags, including Special hashtags, we now allow their use if they've been added to an approved pending message sent from a non-moderator. This means they were added by the approving moderator before the message was approved.

March 6, 2020

  • API: Most endpoints now support the extended=true parameter.
  • API: Endpoints /unbounceuser, /deleteprofilephoto, /resendconfirmationemail now require a POST request along with csrf token.
  • API: Added additional documentation around extended=true parameter.
  • API: Added token parameter to /login endpoint to allow generation/login using HTTP Auth instead of a cookie.
  • CHANGE: When creating a group, if the user has a timezone set, we use that for the default timezone of the group.
  • BUGFIX: In some cases where a moderator claimed a pending message and then left a group, an erroneous claiming badge would be displayed on their previously claimed pending messages.
  • API: Added bouncing option for type parameter of /getmembers endpoint.
  • BUGFIX: When your default message sort is newest first, and you click on the oldest month on the group home page, previously it would not go to the first message in the archives as expected
  • INTERNAL: Updated the Let's Encrypt Cert renewal process.
  • BUGFIX: The Github add integration flow did not work with enterprise groups. Also, the Github API is being updated and we needed to upgrade the library we use to access it.
  • CHANGE: Changed more instances of thread in the UI to topic.
  • INTERNAL: Optimize forcedigests process.
  • BUGFIX: In generated ICS files, we were HTML encoding the Organizer field when we should not have. This was causing parsing errors with some calendars.

February 28, 2020

  • CHANGE: Previously, we would force a digest to be created at 10:30pm Pacific Time nightly, if one had not been generated in the previous 6 hours and messages had been sent to the group since the last digest. Now, we force a digest to be created at 6AM local time for each subscriber, based on their timezone, if a digest had not been generated in the previous 6 hours and messages had been sent to the group since the last digest.