Hello everyone! We've just made the first release candidate for version 0.17.0 of GoToSocial Adventurous admins who want to try the new features and help us spotting bugs can get the release from below:
github.com/superseriousbusinesā¦
ā ļø This release contains several 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 few seconds and an hour or even more (on slower hardware / big databases). Please be patient! Back up your database file before updating! We had to rejig the entire statuses table to introduce interaction policies (see below). ā ļø
Release highlights:
- Interaction policies: This release gives you the ability to set interaction policies on your statuses using the settings panel. Interaction policies let you determine who can reply to, like, or boost your statuses. You can accept or reject interactions as you wish; accepted replies will be added to your replies collection, and unwanted replies will be dropped. This feature is still a work-in-progress as we will almost certainly have some kinks to work out in terms of implementation etc, but we wanted to get it into people's hands as quickly as possible.
User docs here: docs.gotosocial.org/en/latest/ā¦
Federation docs here: docs.gotosocial.org/en/latest/ā¦ - Much wider range of support for different media types: In this release we've embedded a webassembly build of ffmpeg into the GoToSocial binary, so that users can post many different types of media than previously, including mp3, flac, and other audio types, and many more video types. Admins: you don't need to have ffmpeg installed on your server for this to work.
- Audio player: to complement the new media types, we adapted our current video player to also play audio, so people visiting your profile can play MP3s and FLACs. Album art is supported when embedded in the audio file!
- Header/avatar alt text: You can now set alt-text for your avatar + header images, so that screenreader users visiting your profile can read a description of your beautiful face.
- Better threading model for statuses: On the web view of a thread, conversations are now indented at different levels, to make it easier to see who's replying to whom.
- Prefers-reduced-motion is now supported, so that folks with animations turned off in their operating system or browser aren't confronted with lots of animation when they open your profile.
- Conversations view: You can now view a list of your direct message conversations, making it much easier to keep track of who you're talking to.
- Import/export csv files: It's now possible to import Mastodon-compatible CSV files for accounts you follow and accounts you block, making it much easier to migrate across instances. Export of these files is supported too.
- Exclusive lists: You can now mark lists as "exclusive", which means that posts from accounts in an exclusive list will show up only in that list and not in your home timeline.
- Show/hide posts on your profile: Previously only Public posts were shown on your web profile. This is still the default, but you can now choose to show unlisted posts on your web profile too (the Mastodon default), or to show no posts at all.
- Lots of new themes: solarized, brutalist, ecks pee, and more.
- Store worker queue on restart: when you stop the instance, pending tasks are stored into the database, and loaded again when you start up the instance, so that no tasks get lost between restarts.
Thanks for reading!
reshared this
GoToSocial
in reply to GoToSocial • • •GoToSocial
in reply to GoToSocial • • •Thanks for helping us find bugs everyone! You've found some good ones so far and all the bug reports have been very specific and helpful, which is great! ^_^ We're working away on squashing them in preparation for v0.17.0-rc2.
One thing we've noticed so far is that some folks have struggled with the database migrations from 0.16.0 or below to 0.17.0-rc1. This is a reminder to please please please back up your database before doing this update, and also please please be patient and let the migrations run.
It's a huge set of migrations because we had to change big chunks of the statuses table for the new features, and for storage-saving reasons. If your database is small and new you probably won't even notice the migrations but if it's a large-ish database of a few GB and you're running on a low-powered machine they might take bloody ages.
If the migrations fail, running them manually is a huge pain in the arse, so the best bet is always to just restore your pre-update backup and try again; this is why we added the "back up your database" steps to the update instructions.
If you're running in very resource-constrained environments (ie., 512MiB ram machines, machines where you're pushing up against your disk size limit), you may want to free up a bit of overhead before doing the migrations, as we've seen (on SQLite) that they can be a bit demanding.
Anyway! As stated above, most people haven't had problems, but better safe than sorry!
Thanks for reading ā¤
GoToSocial
in reply to GoToSocial • • •Hello again! We've just made the second release candidate for v0.17.0!
github.com/superseriousbusinesā¦
We fixed some bugs! Quite a few bugs actually. And we snuck a new theme in there, and updated the way we distribute Accepts of interactions.
If updating to this release candidate from 0.17.0-rc1, there's just one little database migration to run, which should be quite fast.
For instructions to update to this release candidate from versions prior to 0.17.0-rc1, please read the release notes for v0.17.0-rc1 carefully, but replace all occurrences of
rc1
withrc2
.If updating from 0.16.0 to this release candidate, there are several config file changes and some very large database migrations that will have to run.
Thanks for reading!
GoToSocial
in reply to GoToSocial • • •GoToSocial
in reply to GoToSocial • • •Hiya! Third and hopefully final release candidate for v0.17.0 of #GoToSocial:
github.com/superseriousbusinesā¦
Fixed a couple cheeky bugs related to status web views and pending replies not being marked pending correctly.
For instructions to update to this release candidate from versions prior to 0.17.0-rc1, please read the release notes for v0.17.0-rc1 carefully, but replace all occurrences of rc1 with rc3.
If updating from 0.16.0 to this release candidate, there are several config file changes and some very large database migrations that will have to run.
Thanks!
GoToSocial
in reply to GoToSocial • • •So far we've seen that there may be some memory issues for FreeBSD users running their instances with SQLite. The issue is that memory usage is far higher than it should be on those specific setups. We're currently investigating why this might be happening.
If you are one of the unlucky folks running into this issue, could you please try using this alternative build of the GoToSocial release candidate that we just uploaded, which uses a different SQLite driver?
github.com/superseriousbusinesā¦
If the issue is resolved with that build, please let us know :)