v0.17.2 Ridiculously Selective Sloth

Here's bugfix version 0.17.2 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.2 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.1, or 0.17.0, follow the instructions below.

Release highlights

• Small filter bugfixes.
• Some small tweaks to /api/v1/instance and /api/v2/instance
• Better support for soundless webm files

Migration notes

Upgrading

To upgrade to v0.17.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.
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.2 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

The configuration file has changed since the previous release.

• Add media-image-size-hint with a default of 5MiB.
• Add media-video-size-hint with a default of 40MiB.

You can see a diff of the config file here: v0.17.1...v0.17.2#diff-c071e03510b2c57e193a44503fd9528a785f0f411497cc75841a9f8d0b1ac622

Database Migrations

⚠️⚠️⚠️

This release may contain database migrations which will run the first time you start up this new version.

Be sure not to interrupt this migration process.

This will take anywhere between a couple seconds and ten minutes or more (on slower hardware).

Please be patient!

⚠️⚠️⚠️

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.2
Linux	Armv8/ARM64 (64-bit)	🟢 Full	linux_arm64.tar.gz	superseriousbusiness/gotosocial:0.17.2
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.2-moderncsqlite
Linux	Armv7/ARM32 (32-bit)	🟡 Partial2	linux_armv7_moderncsqlite.tar.gz	superseriousbusiness/gotosocial:0.17.2-moderncsqlite
Linux	Armv6/ARM32 (32-bit)	🟡 Partial2	linux_armv6_moderncsqlite.tar.gz	superseriousbusiness/gotosocial:0.17.2-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

• f3b2eca: [feature] add support for hinting via api/v_/instance preferred image / video max sizes (#3505) (@NyaaaWhatsUpDoc)

Bug fixes

• d8a8386: [bugfix] incorrect /api/v_/instance domain uri fields (#3477) (@NyaaaWhatsUpDoc)
• 7ec6509: [bugfix] support classifying correct video codec without audio as webm (#3494) (@NyaaaWhatsUpDoc)
• 8f288f1: [bugfix] determine mime-type to use during ffprobe evaluation stage, don't bother checking against file extension (#3506) (@NyaaaWhatsUpDoc)
• e953d80: [bugfix] Fix setting immediate expires_at value on filter endpoints (#3513) (@tsmethurst)

Chores & version bumps

• 8f4a96c: [chore]: Bump github.com/tdewolff/minify/v2 from 2.21.0 to 2.21.1 (#3489) (@dependabot[bot])
• e86592b: [chore] pull in go-ffmpreg v0.4.1 (#3485) (@NyaaaWhatsUpDoc)
• 1954ccb: [chore]: Bump github.com/minio/minio-go/v7 from 7.0.78 to 7.0.79 (#3488) (@dependabot[bot])
• c8647f7: [chore] Bump http-proxy-middleware from 2.0.6 to 2.0.7 in /web/source (#3481) (@dependabot[bot])
• 3b037d1: [chore] Bump elliptic from 6.5.7 to 6.6.0 in /web/source (#3495) (@dependabot[bot])
• 49eb8f6: [chore] Fix minor typo in About template (#3502) (@fl4nn)
• d2820a1: [chore]: Bump github.com/minio/minio-go/v7 from 7.0.79 to 7.0.80 (#3511) (@dependabot[bot])
• 51cb6ca: update go-sqlite3 => v0.20.0 (#3483) (@NyaaaWhatsUpDoc)
• 53aaeb1: previously we were using the ffmpeg runner for ffprobe 🤦 (#3512) (@NyaaaWhatsUpDoc)

Documentation

• cad76b8: [docs] Clarify what Visibility Level means (#3500) (@untitaker)
• 17fdce2: [docs] Fix typos (#3498) (@jimt)