Skip to main content

Right, before I dig in too far, can anyone comment to the stability of #GoToSocial these days, as well as how well it's kept up with compatibility with the Mastodon API? Also, person number 389 here saying that it would be great to have a spreadsheet of all of the various fediverse software and how they're different from one another.
#GoToSocial
in reply to Tristan

Talon
Talon
• •
Been running it on a test instance for half a year or so. Maintenance is very easy. Mastodon compat is good and improving. If you don't need any bells and whistles it's definitely the way to go. Runs just fine on the smallest hetzner vm for very low cost. With all the weird stuff surrounding all of the misskey forks it'd probably be where I'd go if I wanted to get away. It doesn't have any clients or even a web interface so mastodon client compatibility is pretty important.
in reply to Tristan

Erion
Erion
• •

It's as stable as slowly improving alpha software can be.

Mastodon compatibility depends on how much of it you need. The good news is that since it has a very minimalistic web interface, the main way to interact with the fediverse is via the API. Parts of it still don't work, for example certain clients have issues with lists, or bringing up the list of DMs you received, etc. Audio attachments are not seamless yet, mutes don't work, notifications don't display via certain clients. Just to mention a few.

It definitely works though and it's usable, and very typical of programs written in Go, it's reasonably easy to maintain while being probably the most lightweight server after Snac2.

⇧