SuperSeriousBusiness GoToSocial

Hello everyone, after a week or two down the release candidate mines, we've emerged blinking into the light carrying with us #GoToSocial v0.18.0 Scroingly Sloth!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.0

Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migrations so you will need to be patient when upgrading, and backup your database first!!

Release highlights

• Status edit support: one of our most-requested features! You can now edit your own statuses, and see instance edit history from other accounts too (if your instance has them stored).
• Push notifications: probably the second most-requested feature! GoToSocial can now send push notifications to clients via their configured push providers.
  You may need to uninstall / reinstall client applications, or log out and back in again, for this feature to work. (And if you're using Tusky, make sure you've got ntfy installed).
• Global instance css customization: admins can now apply custom CSS across their entire instance via the settings panel.
• Domain permission subscriptions: it's now possible to configure your instance to subscribe to CSV, JSON, or plaintext lists of domain permissions.
  Each night, your instance will fetch and automatically create domain permissions (or permission drafts) based on what it finds in a subscribed list.
  See the domain permission subscription documentation for more information.
• Trusted-proxies helper: instances with improperly configured trusted-proxies settings will now show a warning on the homepage, so admins can make sure their instance is configured correctly. Check your own instance homepage after updating to see if you need to do anything.
• Better outbox sorting: messages from GoToSocial are now delivered more quickly to people you mention, so conversations across instances should feel a bit snappier.
• Log in button: there's now a login button in the top right of the instance homepage, which leads to a helpful page about clients, with a link to the settings panel. Should make things less confusing for new users!
• Granular stats controls: with the instance-stats-mode setting, admins can now choose if and how their instance serves stats via the nodeinfo endpoints. Existing behavior from v0.17.0 is the default.
• Post backdating: via the API you can now backdate posts (if enabled in config.yaml). This is our first step towards making it possible to import your post history from elsewhere into your GoToSocial instance. While there's no way to do this in the settings panel yet, you can already use third-party tools like Slurp to import posts from a Mastodon export (see Slurp).
• Configurable sign-up limits: you can now configure your sign-up backlog length and sign-up throttling (defaults remain the same).
• NetBSD and FreeBSD builds: yep!
• Respect users prefers-color-scheme preference: there's now a light mode default theme to complement our trusty dark mode theme, and the theme will switch based on a visitor's prefers-color-scheme configuration. This applies to all page and profiles, with the exception of some custom themes. Works in the settings panel too!

Thanks for reading! And seriously back up your database.

Hi everyone!

We've just pushed a very important security bugfix release for #GoToSocial v0.17.3 and below:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.17.4

If you are running on GoToSocial v0.17.3 or below, you should update to v0.17.4 as soon as possible. It's a very small update from v0.17.3 -> v0.17.4 as it contains only some code logic changes, and no database migrations.

In short, when a dereferencing bug is triggered under a specific set of circumstances it can cause loss of account data on affected instances. It's a rare thing to be triggered, but when it does happen it really, really stinks, and necessitates restoring from backup or manually editing the database to get things working again. (It's not possible to access or tamper with data by triggering the bug, only destroy it.)

We'll release a proper CVE for this in a couple of days when admins and packagers have had a chance to update.

Please note that folks who are already on v0.18.0-rc1 or latest snapshots are unaffected and do not need to do anything, as the bug occurs specifically in v0.17.3 and below. This means if you prefer to update straight from v0.17.3 to v0.18.0-rc1 then that's also an option; you can follow the release notes for v0.18.0-rc1 in this case.

So! If you know folks on GtS v0.17.3 or below, please let them know that they should take action! Link them to this post if you want! And please boost for visibility :)

Thank you everyone! <3 Computers!

Thanks to the hard work of @cdn0x12, #GoToSocial v0. 18.x includes automated light mode / dark mode switching based on your system light mode / dark mode configuration.

This means visitors to the web view of your profile will be able to read your silly posts in whatever form they're most comfortable with. This works for the settings panel too! The auto switching also applies to "auto" profile themes with separate light and dark modes (not every theme has both dark + light mode counterparts at this point).

Big thank you to @cdn0x12 for this <3

Some screenshots!

Hello nerds!

We've just created the first release candidate for #GoToSocial v0.18.0!

Adventurous admins can find the release candidate and upgrade instructions here:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.0-rc1

Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migrations so you will need to be patient when upgrading, and backup your database first!!

Thanks for reading!

Release highlights:

• Status edit support: one of our most-requested features! You can now edit your own statuses, and see instance edit history from other accounts too (if your instance has them stored).
• Push notifications: probably the second most-requested feature! GoToSocial can now send push notifications to clients via their configured push providers.
  You may need to uninstall / reinstall client applications, or log out and back in again, for this feature to work. (And if you're using Tusky, make sure you've got ntfy installed).
• Global instance css customization: admins can now apply custom CSS across their entire instance via the settings panel.
• Domain permission subscriptions: it's now possible to configure your instance to subscribe to CSV, JSON, or plaintext lists of domain permissions.
  Each night, your instance will fetch and automatically create domain permissions (or permission drafts) based on what it finds in a subscribed list.
  See the domain permission subscription documentation for more information.
• Trusted-proxies helper: instances with improperly configured trusted-proxies settings will now show a warning on the homepage, so admins can make sure their instance is configured correctly.
• Better outbox sorting: messages from GoToSocial are now delivered more quickly to people you mention, so conversations across instances should feel snappier.
• Log in button: there's now a login button in the top right of the instance homepage, which leads to a helpful page about clients, with a link to the settings panel. Should make things less confusing for new users!
• Granular stats controls: with the instance-stats-mode setting, admins can now choose if and how their instance serves stats via the nodeinfo endpoints. Existing behavior from v0.17.0 is the default.
• Maintenance router will now be used while your instance is starting up / running migrations. It serves a nice status page informing visitors to wait while migrations complete. Less admin anxiety! Stuff is working!

#FluConf seems like a great idea. From the website:

FluConf is an (online) event for people that are interested in or involved with Free and Open-Source Software (FOSS) and open culture.

So long as densely-populated in-person events remain an unacceptable risk, we are committed to developing alternatives as a form of harm reduction. FluConf takes place online, and will perhaps be more similar to a reading group or trade journal for those interested in FOSS.

Beyond reducing the spread of dangerous pathogens which are unfortunately commonplace at many traditional conferences, we also aim to foster the inclusion of groups who have been unable to attend such events for a wide variety of reasons. For those who avoid international travel for the sake of the climate, or those for whom the acquisition of a visa is time-consuming and prohibitively expensive, or for a wide range of other circumstances, purely online events where such participants are more than an afterthought can be a way to access opportunities which are often reserved for those with more privilege.

Like unconferences and other somewhat subversive types of event, we aim to develop an organizational format which is cost-effective and easily replicated without highly specialized infrastructure or corporate sponsorship.

Participants can follow along with the event's program on the fediverse by subscribing to the official Mastodon account, which will introduce each contribution as it goes live, and facilitate subsequent discussions about their topics: @fluconf

Lots of very interesting talks in the program: https://fluconf.online/program/

Some highlights:

• Zen and the Art of Multicast - An Inquiry Into Technology and Values
• A luddist criticism of "Open Source"
• Improving Diversity and Inclusion in the Open Source Community
• Neo-Luddism in a developing country can be odd
• Scaling Community Conversations and Decisions

Go see https://fluconf.online/ for more details!

someone's only gone and installed #GoToSocial on their car:

https://masto.doskel.net/@doskel/113884312225881269

We're returning from our holiday and slowly homing in on maybe getting ready to consider looking at possibly doing another #GoToSocial release at some point soon or nearly-soon or whenever we feel like getting around to it.

Likely to be in the next release:

• Post editing: already on main/snapshot.
• Blocklist/allowlist subscriptions: already on main/snapshot. Check out the docs here -- https://docs.gotosocial.org/en/latest/admin/domain_permission_subscriptions/ and here -- https://docs.gotosocial.org/en/latest/admin/settings/#subscriptions.
• Push notifications: not on main yet but vyr has been working hard on this on a branch so we'll try to include it.
• More bugs than ever before, more anti-capitalist homosexuality than you can shake a stick at, more torment collocated at the nexus.

2025 should be good!

Hi all, we're enjoying the peace and quiet of our vacation so much that we're going to extend it a bit longer. We'll be back on or around the 17th of January, at which point we'll reopen the matrix channels and git issues / PRs :)

Thanks for reading, and we hope you're all having a good 2025 so far! ❤️

Good morning or afternoon or evening or night everyone, depending on your timezone! Holiday announcement time!

As we do every year, we'll be taking a chunk of December off from work. This year, our cheeky little holiday will be from the 12th of December up to and including the 2nd of January.

What does that mean, you ask? During that time, we'll make the Matrix help, general, and code channels read-only, and we'll make the Github repository read-only as well. This means that during our holiday period, you won't be able to create issues or pull requests or ask us questions.

We do this to give us time to relax, enjoy quality time with friends and family, play video games, eat gingerbread, drink tea, and pet our various animals, in order to recharge our batteries for the year ahead without worrying about new issues coming in.

This doesn't mean that development work will completely stop for the duration of the holiday, just that the "user-facing" side of the development work will pause, as this is the part that we find drains our nerd batteries the fastest. We are, after all, computer-touching hermits.

So there! It's been a great year for GoToSocial in our opinions, and we're looking forward to working on cool new shit for you all (and for ourselves) in 2025, once we're raring to go again after a break. Thanks for reading! Now pet the sloth:

xoxoxoxo #GoToSocial devs

#GoToSocial: it's basically sort of fine-ish; it's not the worst; it's sort of okay depending on what you need it to do