Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-15 23:41:42)
Hello pals, here's the first release candidate for version 0.22.0 of #GoToSocial:

https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0-rc1

Admins who are feeling adventurous or desperate for the new stuff can try out this release candidate at their leisure.

As always, please read the migration notes carefully for instructions on how to upgrade to this version, in particular note that there are several config file changes that need to be addressed when you're updating from a previous version of GoToSocial to this version, and there are some quite long database migrations as well.

Release highlights

Relay support: GoToSocial now supports subscribing to relays (as an admin action), and pushing posts to relays (configured per-user, with filters available).
Documentation for admin-level relay subscriptions.
Documentation for user-level relays pushes.
Automated cleanup of old remote posts: you can now configure your instance to clean up threads of remote statuses that haven't been interacted with by anyone on your instance. This should save a lot of space in folks' databases!
Documentation for post caching + pruning.
Delivery error tracking for remote instances: there's now a page in the settings panel where admin can view errors encountered while attempting delivery of posts to instances that may be experiencing technical difficulties or may have gone offline. You can use this to get a quick view on possible "dead" instances that you can then remove from your database with a domain block.
Accounts directory: there's a new setting to allow admins to expose (or not) a directory of accounts on the instance! Your account will only be shown in the directory if you opt in via your privacy settings.
Documentation for inclusion in account directory.
Better tracking of deleted statuses/status tombstones: GtS now stores tombstones for deleted statuses, allowing threads to remain intact even when a status in the middle of the thread has been deleted.
Bette
---Reply---
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 00:06:36)
already found one bug with the streaming API when you have a split-domain deployment 🤦

[tobi]

---Replies---

GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 17:45:35)
one bug fixed, we're hunting down the next one (sqlite out of memory error when plenty of memory is available), thanks for all the feedback so far sloth-enjoyers :gtspat: :under_construction: