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!

CC: @pachli@mastodon.social

#snac por otra parte fue más simple y rápido, no tiene una gran estética pero siempre me ha funcionado bien

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 🥰

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!