superseriousbusiness/gotosocial v0.19.2

v0.19.2 Most Seditious of Sloths

on Codeberg

Hello hello, here's version 0.19.2 of GoToSocial.

This is a bugfix release that ensures forward compatibility of GoToSocial v0.19.x with newer versions of Mastodon.

If you are already on a current snapshot / nightly / main version of GoToSocial, do not update to this version, wait for v0.20.0 instead.

If you're updating to this version from v0.19.x, it's a very easy update with no db migrations and just a few small config file changes :)

If you're updating to this version from a version before v0.19.0, please follow the update instructions from v0.19.0, but replace 0.19.0 with 0.19.2 throughout. Be aware that the update to 0.19.x contains some long migrations. Please do read the notes carefully!

Please read the migration notes carefully for instructions on how to upgrade to this version.

Release highlights

• Fixed an issue with interaction policy parsing that made GtS users unable to reply to people on instances that use the canQuote interaction sub-policy.

Migration notes

Pride / trans flags

This release includes a trans flag and a rainbow pride flag in the footer of the GoToSocial HTML.

If you are in a place where it is illegal / dangerous to show such flags, you can remove them by adding the following short custom CSS snippet to your instance-wide CSS at the bottom of the instance section of the settings panel (as admin):

footer nav ul #version span {
  display: none;
}

If you prefer, you can also remove them from the HTML altogether by editing web/template/page_footer.tmpl and then restarting the instance to reload the template. Via Docker you can do this by bind-mounting an edited version of the template file to /gotosocial/web/template/page_footer.tmpl.

We sincerely hope the world becomes a kinder place where warnings like this are not necessary.

Upgrading

To upgrade to v0.19.2 from a previous release:

Binary/tar

1. Stop GoToSocial.
2. Back up your database! If you're running on SQLite, this is as simple as copying your sqlite.db file, eg., cp sqlite.db sqlite.db.backup. On Postgres you can do this with pg_dump.
3. Download and untar the new release, including the web assets and html templates, not just the binary.
4. Edit your config.yaml file if necessary (see below).
5. Start GoToSocial.
6. Wait patiently for any migrations to run, do not interrupt migrations or you could leave your db in a broken state and will have to restore from backup!
7. Enjoy your updated instance.

Docker

1. Stop GoToSocial.
2. Back up your database! If you're running on SQLite, this is as simple as copying your sqlite.db file, eg., cp sqlite.db sqlite.db.backup. On Postgres you can do this with pg_dump.
3. Pull the new docker container with docker pull docker.io/superseriousbusiness/gotosocial:0.19.2 or docker pull docker.io/superseriousbusiness/gotosocial:latest if this is a stable release and not a release candidate.
4. Edit your config.yaml file or environment variables if necessary (see below).
5. Start GoToSocial.
6. Wait patiently for any migrations to run, do not interrupt migrations or you could leave your db in a broken state and will have to restore from backup!
7. Enjoy your updated instance.

config.yaml

No changes since v0.19.1.

Database Migrations

No migrations since v0.19.1.

Which release archive/container should I use?

GoToSocial releases binary builds for 64-bit Linux, FreeBSD, and NetBSD operating systems. We also release Docker builds for 64-bit Linux.

nowasm

For your convenience, we also provide UNSUPPORTED, EXPERIMENTAL BUILDS, created using the nowasm tag, in the downloads list below. There is no Docker build for nowasm.

GoToSocial releases built with nowasm use the Go-native, modernc version of SQLite instead of the WASM one, and will use on-system ffmpeg and ffprobe binaries for media processing.

Using a nowasm build is currently the only way to run GoToSocial on a 32-bit system.

For more information on running a nowasm build, see the nowasm documentation page.

Changelog

Chores & version bumps

• 90851fc97b98e8ac500a0936bc051a4301188ce2: [chore] Use correct policy models (@kipvandenbos)
• 56f98dc3b98d7220947957551ec5aa2f82f9b997: [chore] Update interactionPolicy sub-policy parsing in line with documented defaults (#4229) (@kipvandenbos)