Skip to main content

Search

Items tagged with: pooping


Hi nerds! We've just released #GoToSocial version 0.16.0 Snappy Sloth into the wild. Look at it go! Climbing trees and all sorts, covered in algae, and #pooping once a week.

github.com/superseriousbusines…

Thanks to everyone who helped us comb the bugs out of its fur during the release candidate process. We hope the protein you gained from eating the bugs was reward enough.

As usual, when updating to this version (which you really should, because it's quite good), please read the release notes carefully, particularly the database migration notes; and make sure you don't interrupt the database migrations.

Ta!


Highlights of this release (nothing new since 0.16.0-rc1, just reiterating):

  • Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
    Documentation here: docs.gotosocial.org/en/latest/…
  • Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
  • Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
  • Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
  • Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
  • HTTP header permissions settings: The settings panel now has a section that allows admins to set regular expressions to deny requests depending on HTTP headers.
    Documentation here: docs.gotosocial.org/en/latest/…
  • Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
  • Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
  • Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
  • Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
    Documentation here: docs.gotosocial.org/en/latest/…
  • Email change: Users can now change their email address in the settings panel without admin intervention.
    Documentation here: docs.gotosocial.org/en/latest/…
  • Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.