#GoToSocial v0.21.0 soon probably... first RC in maybe a week or so I'd guess? It's gonna be a nice release (domain limits! among other things):
https://codeberg.org/superseriousbusiness/gotosocial/compare/v0.20.3...main
gotosocial
I didn't notice that #gotosocial added post language support a while back, now on
my Fediverse post migration tool slurp can now import from Bluesky!
i'm looking for beta testers who would like to give it a try, ideally on a throwaway Fedi server like a GTS testrig.
caveats:
currently doesn't check Bluesky's advisory "Discourage apps from showing my account to logged-out users" profile flag: imported Bluesky posts will have public visibility on Fedi
doesn't attempt to translate Bluesky thread gates to GTS interaction policies, because i need to catch up on both first
video alt text is preserved but captions are not, because Bluesky's per-language VTT sidecar caption files would need to be converted and inlined for Fedi servers expecting one file per video
doesn't handle quote posts, because GTS doesn't have quote posts
Looking for testers for a new Mastodon TUI.
tooi is a re-implementation of the TUI included with toot, using a more modern framework which is easier to work with. It supports most features `toot tui` does, and some new ones too.
tooi is set to replace `toot tui` which has proven to be troublesome to support and extend.
The GoToSocial post import tool, slurp, now supports BlueSky post and media imports, backdated and all. I even used a custom PDS.
I'll do a write up at some point.
The most suprising thing, which probably should not have been a surprise - all your BlueSKy posts and media are completely public, and you can grab ANYONE's collection of posts and media if you want....no auth required.
https://github.com/VyrCossont/slurp?tab=readme-ov-file#downloading-and-importing-a-bluesky-archive
Edited 133d ago
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 @Codeberg 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
good morning dorks and nerds! due to an excess of joie de vivre, gregariousness, bon vivantry, whimsy, and childlike wonder, we're going to extend our holiday by a week
what this means: instead of reopening all our codeberg issues and matrix rooms today (Jan 5th), we'll open them next week (Jan 12th) instead
we'll actually probably start doing bits of work already, we just don't quite feel ready yet to fully start Dealing With People again (no offense, you're lovely, just imagine us as sleepy winter bears who haven't had their coffee yet and are therefore blinking drowsily at all requests to be "on")
much love and kisses and happy new year from the #GoToSocial team ❤️ 
Po wielu dniach przygody z wyborem, instalacją i konfiguracjęlą fedi serwera GoToSocial, myślę że to już będzie to. Próbowałom Friendici ale jednak topornie się tego używało, po długim czasie mastodonowania. Swoje kolektywy przerzucę tylko na swojego Mobilizona, bo i eventy tam są i standardowe wpisy (ogłoszenia grup). Może uda się dla niego wydzielić ścieżkę fedi.nemo.earth/groups zamiast używać kolejnej subdomeny.
Pierwotnie byłom na pol.socialu, ale zaczęły mi przeszkadzać częste przerwy w działaniu. Chmurę też swoją już mam xD
No i ponownie się przedstawię:
Aktywiszcze i programiszcze. Prowadzę trzeźwe i wegańskie życie. Jestem niebinarne w trakcie HRT, z adhd i w spektrum autyzmu. Choruję na stwardnienie rozsiane. Gram na perkusji, głównie punkową muzykę. Żyję w Rawiczu i we Wrocławiu. A i używam Arch Linuxa.
#introduction #gotosocial
Edited 129d ago
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.
Anyone have experience using #Snac2 for a small activitypub instance? Currently I use #gotosocial which is great but I'm curious about other options. Running a second instance with a different domain for friends or a second account is appealing to me.
I've seen the raw HTML for some #piefed post content showing in the spoilerText field on some platforms via the mastodon api, including #gotosocial, #neodb (takahe/incarnator) and I think #pleroma. My current kludge is to check the spoilerText for html tags (specifically, a beginning <p>).
Edited 45d ago
according to this as of December 2025 there were 1,632 #GoToSocial instances on the Fediverse, up 400 instances from the same time the year before:
https://prattohome.com/@ottoto2017/115869882336719794
and I keep telling people the sloth is stinky software that shouldn't be used 
i don't know how the @gotosocial folks manage it so consistently, but they have again enabled me to not touch my instance for like nine months, decide out of the blue to yolo a major upgrade, and walk away from the whole thing an hour later, unscathed and posting.
👾Testing an image post again with
media-image-size-hint: 1MiB
In #GotoSocial config.
I am incredibly delighted and impressed to see the domain access subscription feature in #GoToSocial - allowing admins to subscribe to a domain list for allowing or denying domains, and - more importantly - processing retractions when those lists remove an entry 💯
If you are building federated services, please review this feature set:
https://docs.gotosocial.org/en/v0.20.1/admin/domain_permission_subscriptions/
Additionally heartened to see NLNet funding @gotosocial for the addition of new moderation and federation features - congrats!
Fediverse people, need your advice! 🙂
Do you know any GoToSocial servers that are open to public signups?
Would especially like to know about general servers that aren't aimed at a specific niche.
I've had many people asking about joining a GTS server lately, not sure what to suggest as there isn't a "JoinGoToSocial" website anywhere and the official GTS site is aimed at self-hosting people.
Migrated from Sharkey to GoToSocial, because I wanted something more light-weight and less feature-rich (though I do have to say that Sharkey is excellent and has tons of features and control. I highly recommend it to somebody who really wants a lot from their Fediverse software). I probably sent out some unnecessary notifications by mistake while backloading my posts. Sorry about that.
I wrote this python script for doing the actual backloading. It's clunky, doesn't handle many common cases, breaks on mentions, and has tons of little flaws, but it did get the job done.
Hello, we've just done a bugfix release of #GoToSocial v0.20.3, codename "Most Sinister Sloth 😈😈😈😈😈"!
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.20.3
This release contains some bugfixes for annoying little API issues, updates to robots.txt to forbid more so-called "ai" (🤢) crawlers, and a bugfix for polite interaction requests that will be useful when v0.21.0 comes out in a couple weeks.
If you're updating to this version from v0.20.0, v0.20.1, or v0.20.2, 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.3 throughout. Be aware that the update to 0.20.x contains some potentially very long migrations. Please do read the notes carefully!
If you are currently on a snapshot / nightly build, stay on the snapshot / nightly build, as it's already ahead of this release.
Thanks for reading!
the #gotosocial status content_type field is handy - when I see that, I assume there's no embedded markdown in the HTML
gotosocial.social has been updated to #GoToSocial v0.21.0-rc1!
⁃ You can now mark your account as "indexable" by full-text search
⁃ You can opt-in to show reblogs on the web view of your profile
⁃ You can see the reason for undownloaded media
⁃ canQuote property is now included in your posts, this signals intentn for GtS to implement quote toots at some point
⁃ OpenGraph previews of your posts is now much better
Full changelog:
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.0-rc1
https://gts.superseriousbusiness.org/@gotosocial/statuses/01KH6H52VWPS2N6G0ZFD08NXMT
Hello, here's the second release candidate for #GoToSocial v0.21.0 Sacrilegious Sloth!
https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.0-rc3
What happened to rc2 you ask? Shhhhhhh. Shh. Shush. It's okay. Don't worry about it.
As always please read the migration notes carefully!
For highlights of v0.21.0 please see our previous post about it.
Thanks! Have a nice weekend!
We're looking into implementing interaction controls in #Holos, following the approach proposed by #GoToSocial. This would let you decide who can reply, like, or boost your posts. It fits well with the Holos philosophy of giving you full control over your online presence. More details here: https://docs.gotosocial.org/en/latest/federation/interaction_controls/
In #ActivityPub, once a post is federated, you lose control over how remote instances handle interactions on it. Some servers like #GoToSocial are working on interaction controls, but non-compatible instances simply ignore your rules.
With #HolosSocial, we're considering a "safe mode" available at publishing time. Your post would only be delivered to followers on instances that respect interaction controls. Not enabled by default, but there for those who need it.
Is anyone else using #snac / #snac2 seeing 401s when trying to follow #gotosocial accounts, or is it my own configuration?
First I thought it was some rejection of my instance since I changed server, but since I've noticed it happens even with instances I hadn't seen before.
First I thought it was some rejection of my instance since I changed server, but since I've noticed it happens even with instances I hadn't seen before.