Groups.io: Changelog
November 6, 2026
Site-wide
- CHANGE: When a page couldn't be loaded, clicking its link or tab seemed to do nothing. Now, if the page has an error, the error page is shown. If the site can't be reached, or doesn't answer within 30 seconds, a message says the page could not be loaded, with a Retry now link. If saving a form fails, a message says your change was not saved.
- BUGFIX: A link in the content of a group page that went somewhere with a different sidebar (another group, a subgroup, Your Groups or your account settings) opened that page under the first group's sidebar, so the sidebar and its links were wrong. These links now load the whole page.
- BUGFIX: If you clicked a link and then another before the first page had loaded, a slow first page could replace the one you picked last. Going back while a page was still loading had the same problem. The page you picked last now always wins, and a form you were saving still finishes saving.
- BUGFIX: After saving a form that stays on the same page, such as a group's Settings, "Your changes have been saved." appeared twice, and every later notice on that page appeared twice as well. Each notice now appears once.
October 30, 2026
Site-wide
- BUGFIX: The captions on the color pickers for hashtags, events, database columns and a member's color were never translated. They now appear in the member's language once translations are updated.
October 16, 2026
Site-wide
- BUGFIX: Quotes and other special characters in topic subjects, file and folder names and descriptions, chat member names, and pending message senders could break the menus and confirmation windows that use them. These are now handled correctly everywhere.
October 9, 2026
Site-wide
- BUGFIX: When you weren't logged in, clicking "I Agree" on the cookie notice didn't remember your choice, so the notice came back on every page. Your choice is now saved and the notice stays dismissed.
October 2, 2026
Site-wide
- INTERNAL: blockerd now blocks IP addresses with firewall sets on the load balancers instead of an nginx deny list, so adding or removing a block no longer reloads nginx.
September 25, 2026
Site-wide
- DOCS: Updates from Nina.
September 18, 2026
Site-wide
- CHANGE: Email addresses ending in @ilands.app are banned. https://beta.groups.io/g/main/message/41191
September 11, 2026
Site-wide
- API CHANGE: The API reference now has search, endpoint summaries, clearer parameter requirements and limits, expandable response examples, and named request examples. An editable request builder generates cURL, Go, and JavaScript code, and remembers the selected language. The layout, navigation, and code formatting are also improved on phones and in dark mode.
- API CHANGE: Corrected request examples for
/gettopicsand/updatepoll, and removed unsupported example parameters from/getfeedand/getpoll. The documentation now clarifies how omitted and empty values affect/updatewebhookand that/deletedatabaserowreturns an empty HTTP 200 response.
August 29, 2026
Site-wide
- API BUGFIX: Paginated API endpoints treated an invalid or out of range
page_tokenas the first page while still reportinghas_more, so a client with a bad token would loop over the first page forever. Such a token now returns an empty page withhas_morefalse. https://beta.groups.io/g/api/message/467 - API BUGFIX: The last page of
/gettopicsresults within a group reportedhas_morealong with anext_page_tokenthat was not a valid cursor, causing aninvalid_valueerror when used. Paging through a group's topics now terminates cleanly. - INTERNAL: The browser error reporter could not deliver a report when the site's JavaScript bundle failed to download, because the reporter itself depended on that bundle — so real users with failed loads were invisible, while scraper bots (which inject their own jQuery) flooded the log with the follow-on errors. The reporter now uses a transport of its own, sends a single classified
bundle-load-failurereport naming the script that failed, suppresses the cascade of "not defined" errors that follow a failed bundle, and records whether the reporting browser had a session cookie, separating members from bots at a glance.
1 - 15 of 15
- previous page
- 1
- next page