dusty.ninja

From a Hawaiian language text

⚠️⚠️⚠️ SQLITE USERS SHOULD SKIP THIS RELEASE CANDIDATE AND GO STRAIGHT TO v0.22.0-rc2! There's a bug in rc1 that causes migrations to fail. Postgres users are unaffected. ⚠️⚠️⚠️

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

Anthropic, on their quest to achieve market supremacy via regulatory capture and hyping the dangers of AI, has managed to get the leopards to eat everyone’s faces.

Now they can’t sell their new products to anyone.

Look forward to the “upload your passport picture and two notarized sworn affidavits” to be part of the onboarding workflow.