Anyone know a good #GoToSocial instance they can recommend? Run by decent people, nice community, etc?

@poes kalo gak ada join relay, tips dari kawan-kawan #gotosocial sebelum bisa join relay, minimal follow @language-id pake akun dummy di instance ente. Biar dapat masuk postingan-postingan bahasa indonesia

So.....

Mari kita aktifkan https://relay.fedi.buzz/language/id

@kongtol@gts.sangeunahna.com @sakeudeung@gts.sangeunahna.com minggir dulu ya, kalian kan kaum #gotosocial yang ribet kalo mau pake relay 🤣

#fediverse #relay #relayserver #fedibuzz

@dumpsterqueer indeed it does, updated my instance to the latest snapshot last night. Looks good so far! @kim #GotoSocial

My GoToSocial instance at gts.snakepit.us now has open signups with manual approval. If you have ever wanted a quiet, hand-moderated corner of the fediverse, here is how joining works:

1. Fill out the form at https://gts.snakepit.us/signup. Pick a username, add an email, and write a few sentences about who you are and why you want in. The reason matters: it is what I actually review.

2. Your request lands in my moderation queue the moment you submit, and I approve or deny it by hand. No email verification loop, no waiting on a robot.

3. Once approved you sign in with your email and password and you are done. Use any fediverse app you like, or Sidewinder (gtsweb.snakepit.us), the client I built for the instance: installable PWA, push notifications, a catch-up digest for when you have been away, and full keyboard navigation.

What the instance is: small, on my own hardware at home, nightly backups, no algorithm, no ads, no tracking. I vouch for people one at a time instead of running an open door, which is exactly why the form asks for a reason. This is essentially what I have been doing for DMV.Community for years and it has worked well for keeping it peaceful and friendly here.

If that sounds like your speed, come join.

https://gts.snakepit.us/signup

#GoToSocial #Fediverse #ActivityPub #Mastodon

Hi fediverse,I could use some advice, is there a way to "self destruct" a GoToSocial instance I selfhost ? similar to how Littlefedi does it. I have no issue with taking the GTS instance offline but I've heard it is bad fediverse etiquette to let a deleted instance, posts linger without a server to connect to.

#gotosocial
#fediverse

Something I have noticed is I tried to follow two different #gotosocial accounts on different servers and they both fail leaving 401 in the admin queue.
Is this a known issue with gts @stefano@mastodon.bsd.cafe ?

**NEBUVERSE – Mein eigenes Stück Fediverse**

Darin geht’s um meine eigene kleine GoToSocial-Instanz auf Worldnode:

Warum ich sie gebaut habe, wie ich GoToSocial ohne Docker auf Debian 13 eingerichtet habe, wie WebFinger, Relays und nginx zusammenspielen – und wie ich Speicherverbrauch, Backups und Restore-Tests gelöst habe.

Kein „Selfhosting ist Magie“-Gelaber, sondern mein echter Aufbau mit echten Messwerten und den Dingen, über die man beim Basteln wirklich stolpert.

🔗 https://www.dennishilk.com/de/blog/nebuverse-gotosocial-selbst-hosten/

#Fediverse #Mastodon #GoToSocial #SelfHosting #Linux #Debian #OpenSource #Homelab #ActivityPub #WebFinger

Alt...

Collage-Grafik zum Blogartikel über NEBUVERSE. Groß im Bild steht „NEBUVERSE – Mein eigenes Stück Fediverse“. Daneben sind mehrere echte Screenshots der selbst gehosteten GoToSocial-Instanz zu sehen: das öffentliche Profil, die Einstellungen, die Speicher-Telemetrie und die Instanz-Startseite. Unten stehen die Hinweise „realer Aufbau“, „getestete Backups“ und „echte Metriken“. Das Design ist dunkelblau mit technischen UI-Elementen.

Over the day I spend some time to get gotosocial running using helm in k3s. It works in a sense that it loads and I can set some options. But it is far from stable. So I need to look into this at some later date and/or look at alternatives. Snac is on the shortlist too. I used it previously on top of OpenBSD and it was fine.

#gotosocial #fediverse #k8s

@bentsukun I think I tried it like a year or two ago, for my #GoToSocial instance. I don’t remember exactly what I didn’t like but I finally settled for Ivory and have yet not find any greater competitor on iOS.

Post your #NeverSlop tech stack!

I'm thinking...

• OS: #NetBSD, #Illumos, #Haiku, #RedoxOS or #9front
• Editor: #ed, #nvi, or #VimClassic
• eBooks: #clbre??? (Doesn't seem to have any downloads yet); #arcalibre?
• Social: (egad, #Mastodon is already sloppified?!?) #GoToSocial, #snac2, hopefully #LittleFedi
• Audio editing: #Tenacity
• Browser: #KonformBrowser
• Image editing: libvips
• Data/file encryption: #LibreSSL, ccrypt
• Email: #aerc, #clawsMail

(I haven't tried all of these yet)

I like Mastodon, I really do. But it has so, so many dependencies, and updating it on illumos or OpenBSD is getting really difficult, release after release.

Some dependencies are primarily distributed as binaries, or only build on Linux and macOS. It's not Mastodon's fault, but it depends on them.

That’s why, in my opinion, solutions like snac, GoToSocial, or littleFedi have a reason to exist: all of this is much, much easier...

#Fediverse #snac #GoToSocial #littleFedi #OwnYourData #Mastodon

RE: https://rpi0w.stefanomarinelli.it/@stefano/01a0448d-c9e8-7b7e-a225-b22fc0333f0f

Mastodon is great. But littleFedi, snac, GoToSocial, Mitra, Akkoma, etc. - they all share a mission: make sure people will be able to self host their instances without investing a huge sum.

#Fediverse #Mastodon #littleFedi #snac #GoToSocial #Mitra #Akkoma

Have a look at #GotoSocial, or #snac or even #LittleFedi - all perfectly hostable even from Raspberry Pis. And if you are only interested in hosting one to a handful accounts you won't miss anything from Mastodon. Although GotoSocial can also hosts 1000s of users (the other two mentioned, less so)

I just adjusted my relay instance which now also finally supports #GoToSocial! Of course, it also supports Pleroma, snac, Mastodon, littlefedi, starling and many other ones!

With relays, your own posted content gets distributed to all connected instances, as well you get the content all other instances. Currently, mostly tech related instances are connected, focusing on #Linux, #Proxmox, #BSD / #FreeBSD, #IPv6 and many other things!

More information at: https://fedi-relay.gyptazy.com

#socialmedia #fedi #fediwall #fediverse #activitypub #activitypubrelay #relay #social #snac #snac2 #mastodon #gts #gotosocial #littlefedi #pleroma #misskey #services #devops #starling #tech

There is a person I've been helping for a while who runs two instances, one #GoToSocial and one #snac.

Yesterday, they suffered severe file system corruption on their device, and I lent them a hand with the recovery. For GoToSocial, they restored the DB from the previous backup and got it running again. For snac, although a few files were lost, no action was necessary... it just started back up and did what it had to do, bringing the instance back to full operation.

This goes to show that when software is well-designed and intentionally kept simple, it's also easier to get back up and running when something goes wrong. In this case, snac's "files-only" approach demonstrated excellent resilience.

Thanks, @grunfink !

#snac2 #snac #ThankYouTuesday #Efficiency #IT #SysAdmin #OwnYourData

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 @Codeberg!

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/

@kim's massive chore PR to remove #GoToSocial's dependency on Gin got squerged a while ago: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4847

Gin was useful for a while when GtS was in its infancy cuz Go didn't have decent http routing stuff in the standard library back then. But now it does! And not only that, but Gin started accepting LLM contributions recently, so it clearly had to go 🤢

We'll keep monitoring + trying to remove dependencies on "ai"-happy code as we go along; and, as always, we will continue to forbid any LLM-based contributions to GtS itself, because ew, ick, yikes, gross.

Happy slothin'

Self-hosted fedi platform apps
good for single-user servers

#Snac2, #Mitra, #GoToSocial, #Bonfire

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!

I've been on the fence about hosting my own #fediverse account for a while now, mainly because of the insane hardware requirements.

I've considered pleroma/akkoma for a while, but i don't know the first thing about elixir and their docs are not the most clear. I've been really tempted by #GoToSocial, but #snac's easy install & general simplicity made me take the plunge.