GoToSocial

🏳️‍⚧️ 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!

Public Key

npub1rhwjy9flnnfal667lj9xvxp9vq2a9f552pezl0uuur8x7qqu67ys0le0fl

NIP-05 Address

[email protected]

Profile Code

nprofile1qqspmhfzz5lee57lad00eznxrqjkq9wj5629qu30h7wwpnn0qqwd0zgpzpmhxue69uhkummnw3ezuamfdejsz9thwden5te0wfjkccte9ejxjar5duh8qatzceyafh

Publishing to

Author Public Key

npub1rhwjy9flnnfal667lj9xvxp9vq2a9f552pezl0uuur8x7qqu67ys0le0fl

Show more details

Last Notes

2026-10-21 16:25:52 GMT

Hello, we heard everyone has been having a great time with security releases so we're doing one as well. Here's v0.22.3 of #GoToSocial aka Shrubbiest Sloth Ever:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.3
Release highlights
Bump required Go build version to v1.26.10 to mitigate CVE-2026-111943 by distrusting select intermediary authorities so server admins (and docker users) don't have to update ca-certificates themselves (see https://github.com/golang/go/issues/82348).
Fix an issue in the dereferencer where remote accounts could masquerade as other remote accounts with sneaky URL shenanigans. Thanks to @nprofile…97aa for reporting this.
⚠️⚠️ We recommend everyone running GoToSocial update to this release at their earliest convenience. ⚠️⚠️
For everyone already on v0.22.x it's a simple update with no migrations or config changes. For everyone below v0.22.x, see the release notes for migration instructions.
Thanks! Sorry! Thanks!

2026-10-09 16:07:40 GMT

Hello folks!
We've just made a security bugfix release of #GoToSocial, v0.22.2 Shrubbiest Sloth!
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.2
We recommend everyone on v0.22.1 and lower who uses two-factor authentication (2FA) for their account to update to this release ASAP. We fixed a two-factor authentication (2FA) security bug whereby an attacker who already knows a victim's email address + password, ie., the first factor authentication, could bypass having to input a code from an authenticator app, ie., the second factor of authentication, and obtain an OAuth token for that account. This bug only affects 2FA, and again, only in cases where an attacker already knows their victim's email address + password.
Update instructions are in the release notes: it's a nice easy update if you're already on v0.22.x; and if you're already on main snapshots, just update to latest commits and you're good.
Thanks for reading <3

2026-09-01 10:04:01 GMT

hello nerds, can you help #GoToSocial out with a monthly donation to our OpenCollective?
https://opencollective.com/gotosocial
we're trying to get together an income of a few thousand euros a month to supplement @nprofile…r478 and @nprofile…ftzp's work on GoToSocial; currently we're on 1200ish per month, which is amazing, but we'd like to end up around 2400 / month, or ideally more! that will give us a lot more freedom to continue to work on the project full time without having to look in consternation at our bank accounts, and worry about grant money running dry
if we get enough, we can even eventually look at welcoming another developer to the gotosocial treehouse to assist us in pulling bugs off the sloth, combing its hair etc
if you work at a company that would be interested in sponsoring us by sending donations to our OpenCollective, in exchange for a mention / logo on our docs and website, we're very open to that, assuming the company aligns with our ethics (see our code of conduct to get an idea)
to discuss that, you can send an email to [email protected] and we'll talk!
please boost and share, thank you so much for your help!

2026-07-30 11:40:59 GMT

The relay https://relay.toot.io, and indeed any Activity-Relay service that uses the up-to-date version 2.0.11, now works correctly with GoToSocial:
https://github.com/yukimochi/Activity-Relay/issues/117
If anyone is still having trouble connecting to services running the Activity-Relay software, you can:
Gently poke the admins of those relays to update to v2.0.11, which is the only version currently that works with GtS.
Then as GtS admin you can then try removing all previously-created connections to the relay (pushes and subscriptions), and recreating them in order to re-send the Follow activity. You should receive an accept within a few seconds if all goes well.
If you want posts to actually show up on the federated timeline of your instance, don't forget to either tick "match posts by default" when creating the subscription, or create appropriate relay matchers to pick which posts you want your instance to store + timeline.
#GoToSocial

2026-07-23 14:31:15 GMT

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!
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01KY7NNWZ7V2DB3K87Q54FDDY9.png
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01KY7P2YQC4B53PMMA50F27P37.mp4

2026-07-23 07:59:18 GMT

The positive result of the #Codeberg membership votes to ban so-called "vibe-coded" projects from Codeberg (see here) makes us very proud to continue hosting #GoToSocial on @nprofile…mvm4!
Following the votes and changes to the terms and conditions, Codeberg has written up their stance on LLM's and "vibe-coded" projects:
Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.
The blog post is well-written, well-sourced, and worth reading in full:
https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html
Since GtS has a very pointed anti-LLM policy in our Code Of Conduct, it's particularly pleasing to us that Codeberg is now pointing out that users are no longer welcome on Codeberg if they "[send] LLM contributions in violation of project's custom policies". Happily for us, this has not been a recurring problem on GtS as we tend to give off vibes that keep slop-fondlers at arm's length, but it's good to know that our anti-"ai" policy has institutional support now in case it becomes more of a problem in future.
If you want thank Codeberg by supporting them with membership and/or donations you can do so here: https://join.codeberg.org/

2026-07-22 08:23:55 GMT

@nprofile…87tr has published Part One of her Newbie's guide to self-hosting for #GoToSocial
You can read it here:
https://blog.elenarossini.com/a-newbies-guide-to-self-hosting-gotosocial-part-1-installation-and-set-up/
Thanks Elena! :gtspat:

2026-07-20 13:36:18 GMT

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.

2026-07-02 17:17:44 GMT

- reply

Hi everyone!! <3
Over the last week your generous donations to #GoToSocial have brought our OpenCollective budget up from ~€450 per month to the current total estimate of €950 per month!! That's amazing, thank you so much to everyone who has donated, and boosted our fundraising posts (see thread above) :gtspat:
That means we're a lot closer to our initial goal of getting an estimated monthly budget of €2,500 so that Tobi (writing this post) and Kim can pay themselves a supplementary wage of €1,000 each every month.
Can you help us reach €2,500 a month, to make our work on GoToSocial less stressful and haphazard? We have yearly, monthly, and custom donations available:
https://opencollective.com/gotosocial#category-CONTRIBUTE
Thank you again for reading, boosting, and/or donating, everything helps <3
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01KWVME9DWBN2ZZTYP7PERAH04.png

2026-07-02 17:17:44 GMT

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 [email protected] 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.

2026-07-02 17:17:44 GMT

- reply

We just hit the €1,000 / month mark for donations, thank you so much!! That means we're almost halfway to our initial goal of €2,500 per month to pay hosting costs, and to pay Tobi and Kim €1k each as a supplement for #GoToSocial bugfixes + release + maintenance work!
If you want to help us reach that goal, you can donate to our OpenCollective org here:
https://opencollective.com/gotosocial#category-CONTRIBUTE
Even a yearly donation of €12 (€1 per month) helps us. Thank you! <3

2026-06-26 09:04:03 GMT

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 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.
Better status codes + info pages on deleted or hidden statuses: the old 404 page when you try to open a hidden status in the browser has been replaced with a more informative error page.
Way more configurable http server + client options: we've exposed a whole shitload of settings that you can tweak on the HTTP client + HTTP server that GoToSocial uses. We don't recommend changing these, but if you really want to, now you can.
Show your Träwelling status on your profile by setting your Träwelling page as a field value, similar to how our ListenBrainz integration already works.
Allow setting a name for your tokens, and sorting tokens by last used time in the token view of the settings page. Should make it a lot easier to track which tokens you've created, and when they were used by which apps!
Better layout for web view of profiles that hide all posts from the web: it just uses a single-column view now.
Thank you for reading and happy pride 🌈

2026-06-26 09:04:03 GMT

- reply

Thank you so much for all your help so far 😍 Wow!
With the donations we've reached overnight, according to OpenCollective we now have an estimated monthly budget of €727!
For our first goal we're aiming for an estimated monthly budget of €2,500, so that we can pay hosting costs and pay ourselves €1,000 each per month as a basic supplement.
So we're still looking for an extra €1773 per month! Can you help us with a monthly (or yearly) donation?
https://opencollective.com/gotosocial#category-CONTRIBUTE
Thank you so much again for helping to make #GoToSocial development easier + less stressful for us (Tobi + Kim).
:gtspat:

2026-06-26 09:04:03 GMT

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 working on GoToSocial more sustainable, then, we want to be able to pay ourselves--the two most active devs--a basic monthly salary for all the work we do that isn't big headline features. This will allow us to commit time to unglamorous but vital maintenance chores, without the constant background worry that by doing so we're going to end up running out of money at a critical moment. To make this happen, we need your help!
Thanks to all our donors on OpenCollective and Liberapay, we'd accrued enough unspent money over the years to be able to pay ourselves 1,000 EUR each, each month, for the months of February, March, April, and May 2026 (plus a little bit here and there from Liberapay). For transparency's sake, you can see those payouts here.
As you'll see from our OpenCollective budget, however, we don't make enough from donations to keep this up, and indeed at the time of writing we have only 2000 EUR left in our OpenCollective budget, which gives us ~3/4 of a month when accounting for ongoing hosting costs.
And so, we're asking you, dear sweet reader, sexy-ass cool reader, for a donation or two to our OpenCollective pot:
https://opencollective.com/gotosocial#category-CONTRIBUTE
With your help, we want to be able to raise about 2,500 EUR per month, so that we can continue to pay ourselves 1,000 EUR each per month, plus various other costs that are paid out of the OpenCollective.
Thank you for reading this absolute saga of a post, and for considering donating to us. We really appreciate it! :gtspat:

2026-06-25 15:51:13 GMT

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.

2026-06-23 16:56:43 GMT

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 recommend everyone currently on v0.21.2 or lower update to this release, as it contains some important bugfixes related to exif data stripping and malformed AP messages causing mischief.
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!

2026-06-02 21:59:01 GMT

this instance is now connected to the relay at https://rel.re, pushing + receiving posts that use hashtag #GoToSocial specifically :) :gtspat:

2026-06-02 21:59:01 GMT

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.
Better status codes + info pages on deleted or hidden statuses: the old 404 page when you try to open a hidden status in the browser has been replaced with a more informative error page.
Way more configurable http server + client options: we've exposed a whole shitload of settings that you can tweak on the HTTP client + HTTP server that GoToSocial uses. We don't recommend changing these, but if you really want to, now you can.
Show your Träwelling status on your profile by setting your Träwelling page as a field value, similar to how our ListenBrainz integration already works.
Allow setting a name for your tokens, and sorting tokens by last used time in the token view of the settings page. Should make it a lot easier to track which tokens you've created, and when they were used by which apps!
Better layout for web view of profiles that hide all posts from the web: it just uses a single-column view now.
⚠️⚠️⚠️ This release 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! ⚠️⚠️⚠️
@Postgres users: Following the migration, if you encounter slowdown on Postgres specifically (ie., timing out while loading home timeline) you may need to regenerate your Postgres visibility map. Please check our Postgres database maintenance documentation for steps on how to do this using the psql tool.
Thanks for reading <3

2026-03-31 17:06:51 GMT

we're gonna introduce the "I don't want to see or be seen by straight people" feature to #GoToSocial
shipping soon! 🚀 ✨
/April fools joke

2026-03-19 10:57:26 GMT

happy souls "i've got boss weapons" voice: We've got #GoToSocial BUGFIX RELEAAAASE
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.2
Bugfixes and little chores! Check the commits at the link for specifics.
Note that we bumped the Go version number to v1.25 for this release. Normally we wouldn't do this in a bugfix release, but a dependency update (including a bugfix) depended on it, so here we are. Practically speaking you probably won't notice a difference, but it's worth mentioning.
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.2 throughout. Be aware that the update to 0.21.x contains some database migrations. Please do read the notes carefully!

2026-03-04 18:03:37 GMT

Hello dorks!
Here's a bugfix release of #GoToSocial -- v0.21.1 Sacrilegiouser Sloth:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.1
We fixed some bugs! Check the changelog for details :)
Thank you!

2026-02-24 04:31:27 GMT

Hello everyone, version 0.21.0 of #GoToSocial, aka Sacrilegious Sloth, has emerged from the release candidate process, ready to serve your nasty blasphemous posting needs 🥰 :gtspat:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.0
Please read the migration notes carefully for instructions on how to upgrade to this version! There are database migrations and config file changes to be aware of.
Here are the release highlights:
Domain Limits: You can now create domain limits in the admin section of the settings panel, in order to do things like limit + mute all accounts on a domain (except ones you follow), add content warnings to posts from limited domains, mark media as sensitive (or don't download it at all).
Documented here: https://docs.gotosocial.org/en/latest/admin/domain_limits/
Indexable support: You can now mark your account as "indexable" by full-text search, in the settings panel. This will federate your preference to other servers, so that servers with full-text search functionality can include your posts in search results.
Documented here: https://docs.gotosocial.org/en/latest/user_guide/settings/#mark-accounts-posts-as-full-text-indexable
Show reblogs on the web view of your profile (opt-in): A new setting in the settings panel allows you to opt-in to showing posts that you've boosted/reblogged on the web view of your profile. The default setting retains existing behavior (don't show boosts on the web view).
Documented here: https://docs.gotosocial.org/en/latest/user_guide/settings/#include-boosts-on-the-web-view-of-your-profile
Better caching behavior for timelines. The number of database calls when browsing local + public timelines and lists should be significantly reduced.
Store + show reason for undownloaded media: When media fails to be downloaded from a remote instance, the reason why will be shown next to the post.
Include canQuote property on outgoing posts: Currently, this is always set to author-only, but it paves the way (and signals intent) for GtS to implement quote toots at some point.
Much improved OpenGraph previews: Whitespace is now preserved in OpenGraph previews, and media + formatting was rejigged, so linking to GoToSocial posts should result in much better OpenGraph-generated preview cards.
Expand/collapse all spoilers button on web view of threads: when viewing threads in the web view, you can now expand/collapse all spoilers at the click of a button.
S3 Object Info Caching: you can now configure cache.s3-object-info in order to mitigate expensive S3 info calls when doing nightly media cleanup.
Preserve significant whitespaces in incoming + outgoing posts: previously we were squashing a lot of whitespace together, which meant that, for example, indentation could get lost on posts federated into a GoToSocial instance. This is now fixed, so you can post poetry and whatnot without worrying about it looking like hot crap.
Millions of fucking bugfixes: we squashed a lot of them!

2026-02-11 14:07:23 GMT

Hello nerds!
We've just created the first release candidate version of #GoToSocial v0.21.0 Sacrilegious Sloth!
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.0-rc1
Adventurous admins can try updating to this release candidate, and let us know if there's any new and interesting bugs to be found.
We're really proud of this one, the sloth is starting to feel really useable and good!
Please read the migration notes carefully for instructions on how to upgrade to this version. Bear in mind there are a few big-ish database migrations in this one, which may take somewhere between a minute or 20+ minutes to run (depending on your hardware). Be patient, backup your database first, and don't interrupt the migrations.
Release highlights
Domain Limits: You can now create domain limits in the admin section of the settings panel, in order to do things like limit + mute all accounts on a domain (except ones you follow), add content warnings to posts from limited domains, mark media as sensitive (or don't download it at all).
Documented here: https://docs.gotosocial.org/en/latest/admin/domain_limits/
Indexable support: You can now mark your account as "indexable" by full-text search, in the settings panel. This will federate your preference to other servers, so that servers with full-text search functionality can include your posts in search results.
Documented here: https://docs.gotosocial.org/en/latest/user_guide/settings/#mark-accounts-posts-as-full-text-indexable
Show reblogs on the web view of your profile (opt-in): A new setting in the settings panel allows you to opt-in to showing posts that you've boosted/reblogged on the web view of your profile. The default setting retains existing behavior (don't show boosts on the web view).
Documented here: https://docs.gotosocial.org/en/latest/user_guide/settings/#include-boosts-on-the-web-view-of-your-profile
Better caching behavior for timelines. The number of database calls when browsing local + public timelines and lists should be significantly reduced.
Store + show reason for undownloaded media: When media fails to be downloaded from a remote instance, the reason why will be shown next to the post.
Include canQuote property on outgoing posts: Currently, this is always set to author-only, but it paves the way (and signals intent) for GtS to implement quote toots at some point.
Much improved OpenGraph previews: Whitespace is now preserved in OpenGraph previews, and media + formatting was rejigged, so linking to GoToSocial posts should result in much better OpenGraph-generated preview cards.
Expand/collapse all spoilers button on web view of threads: when viewing threads in the web view, you can now expand/collapse all spoilers at the click of a button.
S3 Object Info Caching: you can now configure cache.s3-object-info in order to mitigate expensive S3 info calls when doing nightly media cleanup.
Preserve significant whitespaces in incoming + outgoing posts: previously we were squashing a lot of whitespace together, which meant that, for example, indentation could get lost on posts federated into a GoToSocial instance. This is now fixed, so you can post poetry and whatnot without worrying about it looking like hot crap.
Millions of fucking bugfixes: we squashed a lot of them!

2025-10-13 22:40:58 GMT

#GoToSocial has been approved for NLnet NGI Zero Commons funding for 2026! That is, among a number of other cool projects you can check out here:
https://nlnet.nl/news/2025/20251016-selection-NGI0CommonsFund.html
The blurb for what we'll be working on in 2026 is as follows:
GoToSocial is an ActivityPub social network server, written in Go. It complements existing ActivityPub implementations by providing a lightweight, customizable entryway into decentralized social media hosting. GoToSocial places a high value on ease of deployment and maintenance; this means low system requirements, minimal external dependencies, and clear documentation. GoToSocial empowers self-hosting newcomers to deploy small, personalized instances, from which they connect to others across the Fediverse, using low-powered equipment lying around at home. In this project, the GoToSocial team adds new moderation and federation features to GoToSocial, bringing it towards a version 1.0 release (projected end 2026).
Translated to something more concrete, that means we're going to be working on implementing: relay support, instance limits and mutes, old status cleanup, more easily configurable memory usage, tracking of unreachable instances, better search, and a bunch of performance improvements to keep GtS running well on lower-spec computers. And of course, fixing bugs, and likely implementing a few other cheeky features between the soup and the potatoes (kim is interested in looking at quote posts, for example, and tobi will likely do some silly things like the recent ListenBrainz integration).
If things turn out favorably, this chunk of work will bring us towards calling a proper v1.0.0 release by the end of 2026. Ie., we'll finally be able to say "it's good enough to recommend to people".
Thanks for reading! 🏳️‍🌈 :gtspat: 🏳️‍⚧️

2025-10-13 22:40:58 GMT

Hello hello, here's bugfix release v0.20.1 of #GoToSocial, aka More Sinister Sloth 😈😈
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.20.1
If you're updating to this version from v0.20.0, it's a very easy update with no db migrations.
If you're updating to this version from a version before v0.20.0, please follow the update instructions from v0.20.0, but replace 0.20.0 with 0.20.1 throughout. Be aware that the update to 0.20.x contains some potentially very long migrations. Please do read the notes carefully!
Thanks for all the bug reports that helped us find and fix stuff <3
Release highlights
Fix an issue causing duplicate posts to appear in timelines.
Fix RSS format issue.
Speed up some queries a little bit (lists in particular, but home timeline a little too).
Return more sensible HTTP codes from fedi endpoints when things happen that aren't actually errors.
Add API scope for managing emojis.

2025-10-10 06:30:47 GMT

as foretold for many months, now that v0.20.0 of #GoToSocial is released, we have removed our mirror of the code from Github, and removed all our other archived repositories from there as well
all development has been taking place solely on @nprofile…8x0h for months now, we just didn't want to remove our repo from Github immediately when we switched, since people might have been relying on it; so if you hadn't moved whatever mirrors / build systems etc to our codeberg repo yet, you ought to do it

2025-10-05 04:59:18 GMT

Hello everyone!
We've just made the proper release of v0.20.0 of #GoToSocial, aka Sinister Sloth 😈
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.20.0
It's been a long summer of gently poking and prodding at the sloth's tummy and sides to make xem giggle. Now that autumn is here and the weather is getting crisp, xe's finally ready to lumber out the door and say hello. In a sinister manner, that is (it is almost Halloween after all).
Please read the migration notes carefully for instructions on how to upgrade to this version.
The migrations in this release are quite long (can take several hours, even!), as we had to rethread the entire statuses table to handle the new way we cache status threads. Please back up your database before updating, plan downtime accordingly, hang in there, be patient, and don't be tempted to interrupt the migration process!!
Please also pay particular attention to the metrics changes, as we've significantly changed the way that metrics exposure is configured, so you will likely have to adjust your setup if you use GtS Prometheus metrics. For more information on the new way of doing things, look through this document: https://docs.gotosocial.org/en/latest/advanced/metrics/
Release highlights:
Big refactor of timeline code to use less memory and be (hopefully!) more responsive and less error prone.
Support for scheduled statuses!
Support for the focal point property on the frontend + over federation. You can set focal point on your media, now, and have it work properly!
Edit notifications. You'll now get notifications when a status you've interacted with has been edited.
ListenBrainz widget on the web view of your profile, so you can show off the music you've been listening to.
Instructions in the docs: https://docs.gotosocial.org/en/latest/user_guide/settings/#profile-fields
Instance info panel in the settings. Non-admins on the instance can now see which domains are blocked and explicitly allowed, and the reason why.
Bunch of new themes for profile views: hacker dark, hacker light, programmer socks dark, programmer socks light, and ninety-eight.
Option to expose emoji endpoints without authentication. Useful for compatibility with some clients. Default value still requires authentication, don't worry.
Footnotes in markdown!
Configurable thumbnail dimensions. If you want bigger thumbnails that lose less detail, you can do that now.
Federation of avatar + header image descriptions is handled now, both in + out of GtS.
New hidesToPublicFromUnauthedWeb and hidesCcPublicFromUnauthedWeb properties are federated in and out now.
This allows your instance and other instances that support these properties to transmit + respect preferences for the visibility of posts to render on the unauthenticated (public) web view of threads.
Docs for this are here: https://docs.gotosocial.org/en/latest/federation/actors/#hidestopublicfromunauthedweb-and-hidesccpublicfromunauthedweb
Support for avif file format. We forgot to include this earlier, whoops.
Optional JSON logging format, for easier log ingestion.
Atom and JSON feed support for RSS (not just xml).
Reworked metrics format, more + better metrics, and an importable example Grafana dashboard.
Check the docs: https://docs.gotosocial.org/en/latest/advanced/metrics/
Domain permission subscription retractions are now handled properly.
Full changelog is available at the link.
Thanks for reading, and happy upgrading!

2025-04-24 02:06:33 GMT

Now that #GoToSocial v0.19.0 is out, we're going to start the process of transferring our coding workflow from Github over to #Codeberg (@nprofile…8x0h), to get away from Microsoft's endless parade of crapola.
This means that some time in the next week or so, we will "lock" the Github repository so that only superseriousbusiness.org members can create new PRs and issues etc (similar to what we do when we're on holiday).
Then, we will migrate the repository over to Codeberg, using Codeberg's migration functionality to keep issues, pull requests, comments, etc intact.
Once we've validated that everything is in order, we will mark the Github repository as a read-only mirror of the Codeberg repo, and start using Codeberg for issues, pull requests, CI/CD etc.
To avoid breaking people's automated builds that rely on that Github repo, we are planning to keep it as a read-only mirror for a while (eg., 6 months or so, not sure yet) . At some point though we will fully remove it, to avoid contributing our code to Microsoft's "ai" garbage. But we will warn in advance about this so that people can update their scripts and stuff in time.
There will probably be some turbulence in our CI/CD pipelines and workflow and whatnot during this transition period, but nothing that should affect end users of the software: releases up to v0.19.0 will remain available on Github and Docker as normal, and snapshots should remain up to date on our Minio S3 bucket and Docker.
We're looking forward to the move, and to putting the sloth in its new home and seeing it wander around sniffing the furniture and exploring :gtspat: Thanks for reading!

2025-04-21 21:05:27 GMT

What's that coming over the hill, is it a monster? Is it a monster?
Yes actually, it's version 0.19.0 of #GoToSocial, aka Seditious Sloth 😈! It's busted out of the release candidacy process and it's ready to kick some ass.
You can get the release from here:
https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.19.0
Or use either the latest or 0.19.0 Docker tag.
The update contains several database migrations, so please read the migration notes carefully for instructions on how to upgrade to this version!Release highlights
OAuth token scope enforcement: Token scopes (read, write etc) now actually do stuff! So we removed the big "scopes don't do stuff!" warning in the docs. The enforced scopes match the Mastodon API token scopes, so there shouldn't be any surprises for bot owners / app developers.
See https://docs.gotosocial.org/en/latest/api/swagger/ for more info.
Token review / invalidation: You can now review and invalidate tokens issued for your account in the settings panel, to help keep your account secure.
Docs: https://docs.gotosocial.org/en/latest/user_guide/settings/#access-tokens
Create and manage applications in the settings panel: Handy for people who want to run bots and applications with GoToSocial!
Docs: https://docs.gotosocial.org/en/latest/user_guide/settings/#applications
Gallery-style profile layout option: You can now choose to lay out the web view of your profile in a 'gram style gallery. Good for people who mostly post media and want to put that at the forefront.
Docs: https://docs.gotosocial.org/en/latest/user_guide/settings/#select-layout
Support for two-factor authentication (aka 2FA): If your instance isn't configured to use an OIDC provider, you can now secure your account with 2FA via a QR code and an authenticator app. When logging in with 2FA enabled, you will have to provide a time-based one-time password. Security!
Docs: https://docs.gotosocial.org/en/latest/user_guide/settings/#two-factor-authentication
Lots of web view tweaks including nicer media rendering on chrome, proper blurhash support, much better support for keyboard-based page navigation, wider font support for different scripts, tidier status info bar, and more.
OAuth bugfixes should allow more flexibility and compatibility when logging in with or authorizing third-party applications.
bandwagon.fm compatibility fixes: you can now follow Bandwagon.fm artists from your GoToSocial account and receive posts / announcements from them.
Edit domain permissions: you can now edit the obfuscate and public and private comment fields in domain permissions (blocks/allows) instead of having to remove and recreate the permission to update the comments.
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01JSHR8AE84GN4TZ17T5R7MXPG.png
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01JSHR8SBA7H775T50NJG3SAZY.png
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01JSHR8ZZCBN67GN2TV9DYDA7H.png
https://gts.superseriousbusiness.org/fileserver/016VP4S3BP3QSJBACEQ6J1VFDX/attachment/original/01JSHR97859AKNVZVWP435QG47.png