Groups.io: Changelog
January 26, 2018
- BUGFIX: When removing/banning/unbanning someone without a display name or user name, and if you have a user name, your user name was improperly displayed as the banned person's name.
January 19, 2018
- SYSADMIN: Completed reboots of all machines in Phase 1 of Meltdown/Spectre patching.
- CHANGE: Reformatted the calender event popups and added timezone.
- INTERNAL: Began migration off using Redis as a work queue. s3server now using new distributed nsqd system.
- INTERNAL: Updated and added additional features to internal dashboard.
- INTERNAL: No longer using Redis to store LSN/Index versions for esstreamer.
- SYSADMIN: Upgraded Elasticsearch nodes to latest 5.6 version.
- CHANGE: Removed 'Sincerely' from pending email reject message.
- BUGFIX: Changing the non-date parts of a repeating event doesn't result in deleting past events.
- BUGFIX: Changing a repeating event after changing one instance of the event doesn't result in the deletion of that modified instance.
- CHANGE: Better error message when doing an accidental group reply to a topic that's set to sender only replies.
- SYSADMIN: Added an additional search node.
- BUGFIX: The /removemember API call was crashing.
January 12, 2018
- SYSADMIN: Added a second load balancer for redundancy.
- CHANGE: Changed subdomain SPF records in an attempt to track down Outlook spoofing warning message.
- SECURITY: Fixed a case where an attacker could confirm an email address that didn't belong to them.
- BUGFIX: When replying to a digest in an enterprise group, we sent back the wrong error message.
- NEW: Groups now have a default timezone, for new members.
- NEW: The API now returns various counts on the group object.
- CHANGE: Switch default poll response view to the answer table.