Groups.io: Changelog

Subscribe via RSS


December 14, 2018

  • NEW: We are now dropping all email from numbered qq.com addresses, and we treat such addresses as invalid when registering on the website.
  • NEW: In addition to a cover photo, a group can now have an icon. It's currently used only on the mobile home page.
  • BUGFIX: We were not re-writing gmail.com From addresses for senders that did not have 'I always want copies of my own emails' checked.

December 7, 2018

  • INTERNAL: Moved from Grafana to Chronograf for metrics dashboards.
  • NEW: Added advanced subscription option badges to the Delivery column in the Groups page. Also, did some reformatting.

November 30, 2018

  • BUGFIX: We would not display messages correctly if they were plain text only and had a really long line.
  • CHANGE: Text changes to the Update File/Update Folder dialogs in the Files section.
  • NEW: Added advanced subscription option badges to the Delivery column in the Members page.
  • BUGFIX: Changed the included ICS attachment in event notification emails to work around a Gmail bug that would sometimes display one part of a repeating event with the wrong day.
  • BUGFIX: Made checkboxes for moderator/owner notifications screen reader accessible.
  • CHANGE: Because of a policy change at Gmail, we are now re-writing the From line for messages sent back to senders that have gmail.com email addresses.
  • CHANGE: Show your email address in the footers for digests and summary emails.
  • CHANGE: Tweaked the wording a bit on the Yahoo transfer page.
  • NEW: If there is an error adding an email alias, don't collapse the email alias display (which hides the error).
  • NEW: Use the group default time and date format settings when generating event notice/reminder emails.
  • INTERNAL: Unbounced Cox.net members who had been bounced over the past 30 days (because of Cox's email issues).
  • NEW: Now tracking bounce probe deliveries.
  • BUGFIX: In some instances we would send a daily summary to a pending subscriber.

November 16, 2018

  • NEW: We extend expiration of the login cookie each time a person accesses the site.
  • NEW: We have a new, non-expiring cookie that we use to determine when someone has previously been logged in, but whose cookie is now expired. In that case, we redirect the user to the login page, with a banner explaining that their login has expired.