v0.17.1 Very Selective Sloth

Here's bugfix version 0.17.1 of GoToSocial!

If updating to this version from 0.16.0 or below, please follow the instructions for v0.17.0, replacing 0.17.0 with 0.17.1 throughout. ⚠️ Be aware that updating to this version from 0.16.0 or below will involve some serious database migrations. Check the 0.17.0 release notes carefully for more details on this. ⚠️

If updating to this version from 0.17.0, follow the instructions below.

Release highlights

• Fixed a streaming bug which may have been causing issues with some clients like Elk and Ice Cubes.
• Add alt-text/descriptions for default avatar + header images.

Migration notes

Upgrading

To upgrade to v0.17.1 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.
3. Download and untar the new release, including the web assets and html templates.
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.
3. Pull the new docker container (superseriousbusiness/gotosocial:0.17.1 or superseriousbusiness/gotosocial:latest)
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 compared to 0.17.0.

Database Migrations

This release contains one database migration which will run the first time you start up this new version.

Be sure not to interrupt this migration process.

This will probably take only a couple of seconds, though if you're on SQLite, the ANALYZE that's run afterwards may take a bit of time.

Which release archive/container should I use?

Tl;dr: Regardless of whether you're using SQLite or Postgres as your DB driver, you most likely you want the regular version without moderncsqlite in the name.

However, if you're on FreeBSD, 32-bit Linux or 32-bit ARM, we recommend using the moderncsqlite version instead.

You may need to change some configuration options too. See the table below:

OS	Architecture	Support level	Binary archive	Docker
Linux	x86-64/AMD64 (64-bit)	🟢 Full	linux_amd64.tar.gz	superseriousbusiness/gotosocial:0.17.1
Linux	Armv8/ARM64 (64-bit)	🟢 Full	linux_arm64.tar.gz	superseriousbusiness/gotosocial:0.17.1
FreeBSD	x86-64/AMD64 (64-bit)	🟢 Full1	freebsd_amd64_moderncsqlite.tar.gz	None provided
Linux	x86-32/i386 (32-bit)	🟡 Partial2	linux_386_moderncsqlite.tar.gz	superseriousbusiness/gotosocial:0.17.1-moderncsqlite
Linux	Armv7/ARM32 (32-bit)	🟡 Partial2	linux_armv7_moderncsqlite.tar.gz	superseriousbusiness/gotosocial:0.17.1-moderncsqlite
Linux	Armv6/ARM32 (32-bit)	🟡 Partial2	linux_armv6_moderncsqlite.tar.gz	superseriousbusiness/gotosocial:0.17.1-moderncsqlite

FreeBSD

moderncsqlite version currently recommended, though you might have success with the regular WASM SQLite version.

If running with regular WASM SQLite and having instability or memory issues, the following settings may help:

db-max-open-conns-multiplier: 0
db-sqlite-journal-mode: "TRUNCATE"
db-sqlite-synchronous: "FULL"

32-bit

moderncsqlite version is needed, as performance with regular WASM SQLite is not guaranteed when running on 32-bit.

Remote media processing will likely not work with reasonable performance, so you should set the following config variables to prevent download of remote media onto your instance:

media-remote-max-size: 0
media-emoji-remote-max-size: 0

Changelog

Features and performance

• 8a93300: [feature] Add image descriptions for default avatar + header; don't allow editing default desc (#3473) (@tsmethurst)

Bug fixes

• ffc86f9: [bugfix] Fix occasionally streaming empty messages (#3456) (@tsmethurst)
• fab7d17: [bugfix] Fix filter title unique constraint (#3458) (@tsmethurst)

Chores & version bumps

• a48cce8: [chore] Upgrade golangci-lint, ignore existing int overflow warnings (#3420) (@untitaker)
• 9f6a1f7: [chore] Set some additional git attributes (#3454) (@daenney)
• 602c858: [chore] Thumbnail only first frame of animated media (#3448) (@tsmethurst)
• 0d0314b: [chore] Fix loop issue in streaming 🤦 (#3457) (@tsmethurst)
• ea1bf5f: [chore]: Bump github.com/yuin/goldmark from 1.7.6 to 1.7.8 (#3470) (@dependabot[bot])
• f301ec6: [chore]: Bump github.com/tdewolff/minify/v2 from 2.20.37 to 2.21.0 (#3468) (@dependabot[bot])
• e9299e1: [chore]: Bump github.com/prometheus/client_golang from 1.20.4 to 1.20.5 (#3469) (@dependabot[bot])

Documentation

• 3e8c495: [docs] remove duplicate entry from supported platforms (#3442) (@tsmethurst)
• 2a43768: [docs/bugfix] Fix access to /dev and /tmp in AppArmor profile (#3444) (@fl4nn)