Home | Notifications | New Note | Local | Federated | Search | Logout
GoToSocial@gotosocial@gts.superseriousbusiness.org
🏳️⚧️ The official account for GoToSocial news, updates, release announcements, and so on! 🏳️🌈
This is not a support account! Support questions addressed to this account will go unanswered. For support please see the links!
GoToSocial is an open-source, ActivityPub compatible, federated social media server. It's easy to install, lightweight, and runs quite well on small servers 🦥
GoToSocial is still beta software. Your support is appreciated as we fix bugs, add features, and move towards a 1.0 release ❤️
Check out the GoToSocial documentation for more info!
Documentation 📚: https://docs.gotosocial.org
Donate: https://opencollective.com/gotosocial
Matrix space + help channel 💬: https://matrix.to/#/#gotosocial-space:superseriousbusiness.org
Code :win3_setup:: https://codeberg.org/superseriousbusiness/gotosocial
Joined: 2026-06-15 23:47:12
17 notes, 0 following, 0 followers
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-07-23 23:31:15)
DID YOU KNOW: In #GoToSocial, if you go to your account settings and change your layout to "Gram-style", you can set the web view of your profile to show an instagram-like grid of photos to visitors.
This is handy for folks that primarily post photographs or other media and want to highlight that when people visit profile account on the web :)
We wrote this feature quite a while ago but not that many people know about it!
---Attachments---
image: https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01KY7NNWZ7V2DB3K87Q54FDDY9.png
video: https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01KY7P2YQC4B53PMMA50F27P37.mp4
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-07-20 22:36:18)
Hello hello, here's a #GoToSocial bugfix release! v0.22.1 Shrubbier Sloth 🌿🌿!
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.1
If you're updating to this version from v0.22.0, it's a very easy update with no db migrations.
If you're updating to this version from a version before v0.22.0, please follow the update instructions from v0.22.0, but replace 0.22.0 with 0.22.1 throughout. Be aware that the update to 0.22.x contains some serious database migrations. Please do read the notes carefully!
If you're on current main/snapshot, stay there. You already have all the bugfixes from here, and going backwards won't work.
Release highlights
Bug fixes!
Hide instance directory link when directory is not enabled.
Few dependency updates.
Add more gay kissing to the code.
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-07-06 20:02:53)
Hello sloth aficionados!
This is a security announcement for an issue that was fixed in #GoToSocial releases v0.21.3 and v0.22.0. If you are running an earlier version of GoToSocial please find time to upgrade to one of these releases as soon as possible!
The security vulnerability allows a remote attacker crafting (properly signed) ActivityPub activies to send Create, Update and Announce activities to a GtS instance that persist statuses / boosts as if they were written by a remote victim account. This happens due to our (previously) incorrect handling of multi-valued attributedTo and actor in the effected activities. We are not aware of anybody using this vulnerability in the wild, but it remains possible on all GtS versions v0.21.2 and below.
This was kindly disclosed to us by Lain of the Pleroma project, thank you Lain!
Timeline:
June 23rd, Lain emailed admin@gotosocial.org with details of the issue.
June 24th, a fix was merged.
June 25th, versions v0.21.3 and v0.22.0-rc4 including the fix were released, along with a pre-disclosure warning of the security issue urging users to update.
July 6th, security vulnerability publicly disclosed by this post.
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-07-01 17:17:51)
Some updates on relays:
If you're running #AodeRelay and you want it to be compatible with users of #GoToSocial, you can update to the latest version of the AodeRelay software, which contains fixes and workarounds for various issues which were preventing it from working properly with GoToSocial:
https://codeberg.org/asonix/relay
We already know that any relay using the ActivityRelay software does not work with GoToSocial. This includes large relays like relay.toot.io. We're not sure yet why it doesn't work, but it's been almost a year since ActivityRelay was last updated, so we're not sure if it will ever work. We'll investigate this more from GtS's side and see if there's anything we can do.
Relays that we know work right now are FediBuzz, anything using the most up-to-date version of AodeRelay, and rel.re. There might be more, not sure.
@ gotosocial admins: If you have a relay stuck in "approved: not yet" state and you want to retry connecting to it, you can do this by removing all connections to the relay (pushes and subscriptions), and recreating them.
(How this works: when the last connection to a relay is removed, the Follow targeting the relay gets undone. And when you create a new connection to a relay with no prior connections, a Follow is sent targeting the relay.)
We may in future add something that lets you re-send a Follow to a relay without having to remove + recreate all connections, but for now that's how to do it :)
Hope this helps everyone battling to get their relays connecting properly.
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-30 00:29:06)
Hello sloth valuers! #GoToSocial could use your help!
TL;DR, please help us by donating to our OpenCollective page so we (Tobi and Kim) can pay ourselves a basic monthly wage.
Long explanation:
In order to keep work on the GtS codebase buzzing along, Tobi and Kim have to perform the increasingly expensive chore of maintaining their flesh temples by consuming calories, keeping warm and dry (or cool and wet, depending on the circumstances), doing routine bodily maintenance, and so on. Not to mention paying for electricity, internet, etc.
The money we need for all this has so far largely been provided to us by NLnet, the Dutch organization that funds a lot of fediverse projects (among other interesting things). NLnet's support has been of incredible value. Indeed, without it GoToSocial would not exist in its current form; we'd have long since had to get "real jobs" and GtS would have been relegated to being a side project.
However, due to the way that funding from NLnet works, we get paid only for delivering features that we scope out long in advance of when the funding period actually begins. In other words, we get paid every time we merge a big feature, details of which are agreed up to a year beforehand. However, this payout happens only intermittently, since big features take a large amount of time to write.
As everyone who works on code knows, there's more to a project than just writing headline features. We don't get paid for spending time doing things like maintenance, bugfixes, small bonus features, refactoring, triage, helping people in the Matrix chats, code review, and what have you. So, the intermittent way that we get paid means we have to juggle working on very important but unpaid "maintenance" stuff, alongside paid "feature" stuff when our bank accounts start to look worryingly moth-filled. This causes semi-regularly panics in the both of us, as neither of us are particularly resilient when it comes to dealing with financial pressures.
To make wo
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-29 21:33:28)
Hello #GoToSocial enjoyers, after a very fruitful release candidate process (thanks everyone!), we've just released the proper version of GoToSocial 0.22.0, aka Shrubby Sloth 🌿:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0
This is a big feature release that contains support for relay subscriptions and relay push connections, a new instance account directory, better threading using tombstones for deleted statuses,, and support for auto-cleanup of old remote statuses, among lots of other things!
⚠️⚠️⚠️ 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.
This release also contains a long-ass database migration to move status boolean columns (like pinned, local, etc) to a single bitfield column. This saves a lot of space in the database, but it also means on startup the migration has to iterate through all statuses in your database and set the new field. Please be patient and don't interrupt this process! ⚠️⚠️⚠️
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 v
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-25 22:50:21)
Hello everyone, the two releases we announced today (v0.21.3 and v0.22.0-rc4) each contain an important fix for a security vulnerability about which we will disclose more details next week to give people time to upgrade.
In the meantime:
If you're on #GoToSocial v0.22.0 release candidates, please update to v0.22.0-rc4 as soon as you can: https://gts.superseriousbusiness.org/@gotosocial/statuses/01KVYXVTG5BNKEVHJMDYPWGTPC
If you're on #GoToSocial v0.21.2 or below, please update to v0.21.3 as soon as you can: https://gts.superseriousbusiness.org/@gotosocial/statuses/01KVYXQQS1JB0HJEJ060ZAJPQR The update from v0.21.x to v0.21.3 contains no database migrations or anything so it should be very quick + easy.
Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-25 17:20:39)
Hello hello hello, what's all this then? The fourth #GoToSocial v0.22.0 release candidate?
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0-rc4
⚠️ We strongly urge everyone currently using v0.22.x release candidates from rc3 or lower to update to this release, as it contains some important bugfixes related to exif data stripping and a security fix for a vulnerability whereby malformed AP messages can cause mischief. We will make a more detailed post about this vulnerability next week, to give people time to update. ⚠️
Compared to rc3:
Postgres home timeline query performance improvements.
Bugfixes for timelining and streaming relayed statuses (statuses from subscribed relays actually appear in the federated timeline now 🤦♀️).
Bug fixes related to exif stripping and malformed AP messages.
Dependency updates.
Thanks! Have a nice day! Stay cool and crisp!
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-25 17:18:25)
Greetings fellow kids!
We just released v0.21.3 of #GoToSocial, aka Most Sacrilegious Sloth:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.3
This is the last bugfix + dependency update release for v0.21.x!
⚠️ We strongly urge everyone currently on v0.21.2 or lower to update to this release, as it contains some important bugfixes related to exif data stripping and a security fix for a vulnerability whereby malformed AP messages can cause mischief. We will make a more detailed post about this vulnerability next week, to give people time to update. ⚠️
If you're updating to this version from v0.21.x, it's a very easy update with no db migrations.
If you're updating to this version from a version before v0.21.0, please follow the update instructions from v0.21.0, but replace 0.21.0 with 0.21.3 throughout. Be aware that the update to 0.21.x contains some database migrations. Please do read the notes carefully!
Don't switch to this version from current (25 Jun 2026) snapshots or v0.22.0 release candidates. They already have everything that's in here (and more).
Video processing fixes.
Updated robots.txt to tell more bullshit crawlers to fuck off.
Fixed some streaming API stuff.
Bug fixes related to exif stripping and malformed AP messages.
Dependency updates.
Thanks for reading!
Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-19 22:11:06)
Third release candidate for v0.22.0 of #GoToSocial!
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0-rc3
Compared to rc2:
Unfollow relay actor if no connections exist targeting that actor (allows retrying establishing relay connection by removing all connections to an actor + creating a new one).
Fix erroneus use of RelayConnectionCreateRequest when updating a relay push.
Don't error on db.ErrNoEntries in OnMediaDereference callback.
Disable outgoing http2 requests until superseriousbusiness/httpsig is updated, as our signatures were getting messed up by http2 transport.
Only mark status as edited for streaming hooks if edited_at column has changed.
Remove admin check on user-level relay push matchers.
Set statuses-cleanup-remote-older-than to "0s", skip scheduling if 0.
Fingers crossed this is the last one :)
Thanks for all the help finding bugs, everyone <3
Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-17 00:39:53)
As promised here's the second release candidate for #GoToSocial v0.22.0:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0-rc2
Compared to the first release candidate:
Fixed a bug that was causing migrations on SQLite to fail with an erroneous out of memory panic.
Fixed a bug with streaming + assets endpoints on split-domain deployments.
Enjoy! Have fun! Post gay nerd shit! <3
Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 23:51:25)
In case you're interested, it was a single-character bugfix in our go-sqlite3 dependency: https://github.com/ncruces/go-sqlite3/issues/401#issuecomment-4719291828
Big thanks to Nuno for responding so promptly!!
Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 23:50:21)
Alright due to the bug in #GoToSocial v0.22.0-rc1 specifically for SQLite users which causes migrations to fail, we recommend SQLite users wait for v0.22.0-rc2, which we'll be releasing shortly (hopefully within a couple hours). (Postgres users are unaffected.)
Thanks for your patience! And thanks for the bug reporters for notifying us about it! <3
Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 20:21:40)
ooh baby we're figuring it out 👀 :bug_pat:
Reply to @gotosocial@gts.superseriousbusiness.org
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:
Reply to @gotosocial@gts.superseriousbusiness.org
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]
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