Groups.io: Changelog

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.

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.

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.

CHANGE: Email addresses ending in @ilands.app are banned. https://beta.groups.io/g/main/message/41191

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 /gettopics and /updatepoll, and removed unsupported example parameters from /getfeed and /getpoll. The documentation now clarifies how omitted and empty values affect /updatewebhook and that /deletedatabaserow returns an empty HTTP 200 response.

API BUGFIX: Paginated API endpoints treated an invalid or out of range page_token as the first page while still reporting has_more, so a client with a bad token would loop over the first page forever. Such a token now returns an empty page with has_more false. https://beta.groups.io/g/api/message/467
API BUGFIX: The last page of /gettopics results within a group reported has_more along with a next_page_token that was not a valid cursor, causing an invalid_value error 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-failure report 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 - 10 of 10