感谢 CDN18 的出色工作，#GoToSocial 现在有中文文档了！您可以在此处查看中文文档：

docs.gotosocial.org/zh-cn/late…

非常感谢 CDN18！

Thanks to the amazing work of CDN18, #GoToSocial now has documentation available in Chinese! You can view the Chinese documentation here:

docs.gotosocial.org/zh-cn/late…

Thank you very much CDN18!

CDN18 - Overview

Living in the upside-down // Giving it a whirl. CDN18 has 26 repositories available. Follow their code on GitHub.

^GitHub

Hi everyone! We've just made another bugfix release of #GoToSocial, version 0.17.2 Ridiculously Selective Sloth:

github.com/superseriousbusines…

The update fixes a couple small bugs around media processing and filter expiration, and adds media-image-size-hint and media-video-size-hint values to the config file.

Please read the release notes carefully when updating to this version.

Thanks for reading, and have a nice day! Or not, it's up to you; whatever you prefer!

Release v0.17.2 Ridiculously Selective Sloth · superseriousbusiness/gotosocial

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 u...

^GitHub

I really think all servers should expose this info without having to use the API endpoint. #GoToSocial does for example.

Handy tip nonetheless, thank you.

Hiya, we've just done bugfix release 0.17.1 for #GoToSocial.

github.com/superseriousbusines…

Fixes a bug in the streaming API that may have been causing problems for some clients, and adds alt-text for default avatar + header images.

Updating from 0.17.0 is very simple and quick, but if you're updating from 0.16.0 or below then please read the migration notes carefully and be aware of the big database migrations from 0.17.0.

Enjoy!

Mastodon is honestly a resource hog, arguably Ruby is really not meant for web apps. Maintenance is one thing, moderation is another. I don't think the average Fediverse user has any idea how much is out there that we have to deal with so we can foster a safer place for everyone. It is a lot of mental strain from the worst of humanity at times. But it is definitely worth it. If anyone hosts a server, a thank you now and then goes a long way, especially if the service is provided for free.

There are also other servers if anyone does not want to deal with Mastodon, I ran #Pleroma and forks for years, which is lightweight and maintaining the software stack is a lot less involved. Then, there's #GoToSocial, which really can't be compared to anything else, except maybe #Snac. They are just brilliant.

Small, focused instances are always better, so is having more accounts, in case one server goes down. Just my opinion.

My #GoToSocial backup procedure:

This runs as a cron job every day at an off-peak hour. Do bear in mind that both the sqlite backup, which takes place while GTS is running and therefore must handle locks, and xz, take up a lot of CPU power.

#!/bin/bash
umask 027
now0="$(date +'%F %T')"
printf "%s: Starting backup.\n" "$now0"
cd /home/gts/gts || { printf "Impossible to backup. Cannot access directory.\n"; exit; }
mv --backup=numbered instance.back.tar.xz db-backups
printf "Backing up database.\n"
sqlite3 sqlite.db ".backup 'sqlite.db.back'"
printf "Preparing file list.\n"
echo sqlite.db.back > file.list
echo config.yaml >> file.list
echo db-backup.sh >> file.list
echo file.list >> file.list
./gotosocial --config-path config.yaml admin media list-attachments --local-only >> file.list
./gotosocial --config-path config.yaml admin media list-emojis --local-only >> file.list
printf "Tarring up instance data.\n"
tar -cf instance.back.tar -T file.list
printf "Removing auxiliary files.\n"
rm sqlite.db.back file.list
xz -T3 -e --best instance.back.tar
now="$(date +'%F %T')"
printf "%s: Finished backing up.\n" "$now"

Sensitive content Click to open/close

Sensitive content Click to open/close

Hello fellow creatures!

We've finally bitten the bullet and cut version 0.17.0 of #GoToSocial, aka Selective Sloth 🎆

github.com/superseriousbusines…

As always, please read the release notes very carefully when updating, take a database backup, and don't interrupt database migrations no matter how tempted you might be to press ctrl-c. It's not wurf it mate!

Beta release announcement

This is the very first BETA RELEASE of GoToSocial. What does it mean that we're leaving alpha and entering beta? Not much really. It had to happen eventually, and now is as good a time as any to go from "people shouldn't really use this software" to "people can consider using this software but be warned it's not done yet, lots of stuff is missing, yadda yadda". Don't read too much into it!

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 (see screenshots).
• 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.

Supported platforms

We've defined a list of platforms + architectures that we "officially" support and those we partially or don't support due to performance reasons or library constraints, you can check this out right here: github.com/superseriousbusines… If your platform of choice isn't on the list you can, of course, try building yourself, and maybe try the very experimental nowasm tag we recently added, if you're feeling daring: docs.gotosocial.org/en/latest/…

Thanks

Thanks for reading and for your continued support for this silly sloth!

GitHub - superseriousbusiness/gotosocial: Fast, fun, small ActivityPub server.

Fast, fun, small ActivityPub server. Contribute to superseriousbusiness/gotosocial development by creating an account on GitHub.

^GitHub

Hi! Hi there! We've only gone and done another #GoToSocial release candidate innit mate!

github.com/superseriousbusines…

We fixed some small bugs, did a bunch of work around release note generation (not interesting for end users but tobi had fun), and documented GTS_WAZERO_COMPILATION_CACHE and nowasm.

Please read the migration notes carefully!

This is probably the final candidate before the real 0.17.0 release when we officially enter beta, we're all very excited here in the GtS treehouse!

Release v0.17.0-rc5 · superseriousbusiness/gotosocial

Here's version 0.17.0-rc5 of GoToSocial. We fixed a couple bugs! And changed some deployment stuff! And updated some library versions! Please read the migration notes carefully for instructions on ...

^GitHub

Hiya, another day, another #GoToSocial release candidate:

github.com/superseriousbusines…

We fixed a couple small bugs around interaction accepts and rejects :)

Please read the release notes carefully, especially if updating to this release candidate from v0.16.0 or below! There are migrations!

If you're using SQLite on OpenBSD or FreeBSD, please take the release version with moderncsqlite in the name, as described in the release notes.

Thanks for reading and helping us find bugs! We're getting there 🙂

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!

A small compendium of the Fediverse platforms I use/know well.

In the past few days, I revisited some of my old Fediverse instances since some friends asked me to help them set up a new one. I also took the chance to perform maintenance on some leftover instances. Here's my experience:

Akkoma: My oldest instance still running, opened in 2022. It was offline for a few months (3/4). I updated everything to the latest version and restarted it. I’m not sure why, but it’s extremely slow, with a heavy load on Postgres and many queries just to open the main page. I like Akkoma - I'll investigate further.

GoToSocial: I updated a friend's instance - GoToSocial itself was up-to-date, but the underlying system wasn’t. I noticed that once it exceeds 2000 followings, it becomes a bit slow. The database is PostgreSQL, but that's not the issue. The GoToSocial process becomes somewhat heavy on the VPS. Still, it's very usable and a software with great potential, in my opinion. The Mastodon API is implemented quite well and works with the major software.

Mitra: It seems well-built. The person had around 1000 followers and followings on a Mastodon account, which they moved from a large instance. No speed issues, though sending a message makes the server “heavy” for a bit, but it’s temporary. The Mastodon API is partially implemented, but the software is advancing quickly, and I find its native interface quite pleasant.

Snac2: I've always had a soft spot for Snac2. The lack of a database and some design choices make it an excellent solution for small instances. For example, sending posts to all known instances increases visibility and interaction. Its basic, JavaScript-free interface is very clear, though it might not be the best for those used to Mastodon. But the Mastodon API is improving version by version, and I think the developer is doing an excellent job. It struggles a bit with larger numbers, but that's due to the underlying file system, not the software itself. If "move" support (both in and out) were added, I would recommend it to anyone starting self-hosting for single-user or small community instances because "move" is one of the options that gives the most freedom in Fediverse software.

Mastodon: My “old” personal instance was stuck at version 4.1.x and had been offline for a few months. I updated the FreeBSD Jail and upgraded Mastodon to 4.2.12 and then to 4.3.0-beta1. No issues. I also helped a friend (who had an old Pleroma-based instance they barely used) migrate. This user has around 5000 followers and followings - Mastodon is running on FreeBSD on a VPS (arm64) for just over 3 euros a month, with no significant issues (apart from media storage, but that's not Mastodon’s fault). Mastodon is sometimes said to be heavy, and that's partly true, but its modularity ensures that even in cases of overload, queues may slow down, but navigation and the local timeline remain reasonably fast. I think this is a good thing for any larger-scale use of an instance.

In short, I think things are moving in the right direction, and the software is evolving nicely. Well done, devs!

#Fediverse #Akkoma #GoToSocial #Mitra #Snac2 #Snac #Mastodon #SelfHosting #InstanceManagement #FreeBSD #OpenSource

We're getting ready to start creating the #GoToSocial 0.17.0 release candidates, finally :)

We're now running this instance on the latest snapshot, to try stuff out and ensure it's working correctly. So far, it seems good!

To celebrate, here's a couple of MP3s, since it's possible to upload those now. Enjoy! And sit tight for the release candidates in a week or two ^_^

I've been running this single-user instance from October 2022. It's interesting that only this week I went past the threshold of 5000 federated peers. I'm sure this is not even the majority of peers on the fedi (though it probably is the majority of users).

This is not a complaint. I'm not especially popular or interesting and I get plenty of good stuff in my timeline. Rather, it's a reminder to myself that the fedi really has no centre, and the experience one gets of it is really different depending on one's point of access and connections.

Also, thanks to the #GoToSocial team for making it easy to run an instance.

#Pachli 2.6.0 is now available. This version has a new "Suggested accounts" feature to find accounts to follow, improves filter support on #GoToSocial servers, makes parts of the UI more readable, and fixes several bugs.

See pachli.app/pachli/2024/06/27/2… for details.

Thank you to @mileskrell, @kallekn, and @bittin for their contributions to this release.

#AndroidDev

Pachli 2.6.0 released

Pachli 2.6.0 is now available. This release allows you to find new people to follow with a “Suggested accounts” feature, and has the usual bug fixes and other improvements. Read on for more details about these.

^Pachli

Hi nerds! We've just released #GoToSocial version 0.16.0 Snappy Sloth into the wild. Look at it go! Climbing trees and all sorts, covered in algae, and #pooping once a week.

github.com/superseriousbusines…

Thanks to everyone who helped us comb the bugs out of its fur during the release candidate process. We hope the protein you gained from eating the bugs was reward enough.

As usual, when updating to this version (which you really should, because it's quite good), please read the release notes carefully, particularly the database migration notes; and make sure you don't interrupt the database migrations.

Ta!

Highlights of this release (nothing new since 0.16.0-rc1, just reiterating):

• Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
  Documentation here: docs.gotosocial.org/en/latest/…
• Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
• Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
• Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
• Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
• HTTP header permissions settings: The settings panel now has a section that allows admins to set regular expressions to deny requests depending on HTTP headers.
  Documentation here: docs.gotosocial.org/en/latest/…
• Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
• Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
• Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
• Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
  Documentation here: docs.gotosocial.org/en/latest/…
• Email change: Users can now change their email address in the settings panel without admin intervention.
  Documentation here: docs.gotosocial.org/en/latest/…
• Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.

Release v0.16.0 Snappy Sloth · superseriousbusiness/gotosocial

Hello internet! Roll up roll up and see ye all version 0.16.0 of GoToSocial, codename SNAPPY SLOTH. Release highlights Sign up / registration: In this release, you can open your instance to new re...

^GitHub

Hello hello good morning, here's the second release candidate for #GoToSocial v0.16.0!

github.com/superseriousbusines…

We fixed a bug that was preventing brand new instances from federating properly, and a bug where two accounts could refer to each other as moved_to targets.

Get it while it's fresh! 🍞 ☕️

Release v0.16.0-rc2 · superseriousbusiness/gotosocial

Hiya! Second RC for 0.16.0! No db migrations or config file changes between v0.16.0-rc1 and this version, so upgrading is as simple as updating your docker container or stopping GtS, untarring the ...

^GitHub

i made a CLI tool for moving data in and out of GtS and Mastodon instances using the API: github.com/VyrCossont/slurp

it can handle CSV data in Mastodon export format for blocks, bookmarks, follows, and lists. there is no Mastodon CSV format for filters so i made one up. (note that you need to be running GtS 0.15 for filter support.)

it doesn't handle posts or media yet; i have ideas about extending the GtS API to allow backdating posts and suppressing push federation, but probably won't get to that for a while.

#GtS #GotoSocial

GitHub - VyrCossont/slurp: tool for exporting data from and importing data to Fediverse instances

tool for exporting data from and importing data to Fediverse instances - VyrCossont/slurp

^GitHub

Hello everyone!

We've just made the first release candidate for version 0.16.0 of #GoToSocial, aka Snappy Sloth.

github.com/superseriousbusines…

For adventurous instance admins, please read the release + migration notes very carefully when updating to this release, paying particular attention to the database migrations section.

Here are the release highlights:

• Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
  Documentation here: docs.gotosocial.org/en/latest/…
• Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
• Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
• Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
• Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
• HTTP header permissions settings: The settings panel now has a section that allows admins to set regular expressions to deny requests depending on HTTP headers.
  Documentation here: docs.gotosocial.org/en/latest/…
• Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
• Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
• Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
• Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
  Documentation here: docs.gotosocial.org/en/latest/…
• Email change: Users can now change their email address in the settings panel without admin intervention.
  Documentation here: docs.gotosocial.org/en/latest/…
• Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.

Release v0.16.0-rc1 Snappy Sloth · superseriousbusiness/gotosocial

Hello you nerds, dorks, and dweebs ❤️ This here is the first release candidate for version 0.16.0 of GoToSocial, codename SNAPPY SLOTH. Release highlights Sign up / registration: In this release, ...

^GitHub

Oh yes, and v1 of filters is here as well in this release candidate! Depending on the client you're using, you'll be able to add filters to hide certain phrases from posts in your timeline :)

#GoToSocial

Hey nerds! 🌸

First spring time release of #GoToSocial, here's the first release candidate for version 0.15.0 Shagadelic Sloth!

github.com/superseriousbusines…

For adventurous admins updating to this release candidate, please read the migration notes carefully, especially regarding database migrations :)

Release highlights

• Incoming and outgoing Move Activities are now processed properly. This means you will automatically follow other people when they move their accounts, and you can also Move your own account from your GtS instance to somewhere else!
  User docs here: docs.gotosocial.org/en/latest/…
  Federation docs (for devs) here: docs.gotosocial.org/en/latest/…
• You can hide your followers and following collections now! When hidden, your followers/following count will no longer appear on your profile, and your collections of followers/following will be hidden from other servers (and other accounts on your server).
  User docs here: docs.gotosocial.org/en/latest/…
• Preset user-selectable CSS themes are here! In the settings page, you can now choose a theme for your profile, which will change how it appears in the web view of your account! For now we added 5 different themes to choose from, screenshots below!
  User docs: docs.gotosocial.org/en/latest/…
  Docs for admins (how to add your own themes to your instance): docs.gotosocial.org/en/latest/…

#GoToSocial bugfix release v0.14.1!

👢
🐛

github.com/superseriousbusines…

There was a bug in 0.14.0 which was causing SQLite-backed instances to sometimes become unresponsive, with lots of errors in the logs containing interrupted(9) (see github.com/superseriousbusines….

We poked around and this looks like an issue in our SQLite dependency, so we stepped down to the most recent stable version, and also added some code to prevent the problem from rendering an instance unresponsive.

No db migrations or config file changes between v0.14.0 and this version, so upgrading is as simple as updating your docker container or stopping GtS, untarring the release, and starting GtS again.

For instructions to update to this release from versions < v0.14.0, see the v0.14.0 release notes, but replace v0.14.0 with v0.14.1 throughout.

Thanks!

Issues · superseriousbusiness/gotosocial

Fast, fun, small ActivityPub server. Contribute to superseriousbusiness/gotosocial development by creating an account on GitHub.

^GitHub

Hi everyone!

We've just released v0.14.0 of #GoToSocial! Say hello to the Spoiled Sloth

github.com/superseriousbusines…

We're really proud of this release! It fixes a lot of longstanding annoying bugs, and adds some very neat features tooooo

Thanks to everyone who helped us with code and trying out release candidates and filing issues, and a big thank you to all our financial supporters who help us out via opencollective and liberapay :)

When upgrading to this version from a previous release, please note that there are CSS and HTML updates, config file changes, and several database migrations which may take a while to run! So please read the migration notes carefully :)

Release highlights:

• Account aliasing. You can now set the alsoKnownAs field on your account via the settings panel, to indicate other accounts you own. This doesn't do much now, but it's the first step towards the Move implementation for account migration coming in v0.15.0. We originally wanted to include Move in this release but it needs more testing so we pushed it back. Hang in there :)
• Much better thread sorting. Conversation threads on both the web view and client API use a new sorting mechanism which makes them way more readable. No longer will replies in a thread be scattered all over the place.
• Better HTTP signature support. We fixed a longstanding issue with including vs not including query parameters in signed GET requests. We now try (and accept) both methods of constructing signatures. Which leads to...
• Improved thread fetching. You'll see far fewer "orphaned" statuses in your timeline now, and you'll see more replies on statuses from other instances.
• Syntax highlighting for code blocks on the web UI. When you include a code block in your markdown now, and correctly indicate the language the code is written in, it will be syntax highlighted when rendered on your profile in the web UI. This requires javascript, but it's a progressive enhancement feature. Visitors to your profile with javascript turned off will just see the code block without syntax highlighting :)
• Improved "about this instance" page, with a link to the page in the nav bar. Previously the "about this instance" page was more or less hidden. We've now surfaced it better, so you can write all your terms and conditions and instance description stuff there. Relatedly....
• Parse instance descriptions and terms and conditions as markdown. Previously it was very difficult to properly edit these fields, because you had to read + write HTML to do so. Now they're parsed as markdown. This means you can more easily include things like blockquotes, lists, etc.
• Big refactor of HTML templates + CSS. We did a serious rework of HTML templates to fix indentation. Previously if you did "view source" on a GoToSocial profile page, you'd see a mess of sloppily-indented HTML. With this refactor, the HTML is now nicely indented and much more readable. We also did an accessibility pass and tested our HTML with various screen readers to try to make the web view a bit less annoying to navigate.
• First pass at a basic spam filtering system. In light of spam waves happening on the fediverse recently we took a crack at implementing a filter to drop messages identified as spam. This is still in the experimental stage, but it's included in this release so you can try it out already. See the docs for details.

Hi everyone! We just made the second release candidate (rc2) for #GoToSocial v0.14.0. Here it is!

github.com/superseriousbusines…

What happened to the first release candidate, you say? Well, it didn't work properly 🤦 But this one does.

If you're the type of badass admin who uses release candidates, please give it a shot :) If you find any bugs particular to this release candidate, let us know on our issues page so we can fix them before 0.14.0 proper.

As always, please read the migration notes carefully!

Highlights of this release (candidate):

• Account aliasing. You can now set the alsoKnownAs field on your account via the settings panel, to indicate other accounts you own. This doesn't do much now, but it's the first step towards the Move implementation for account migration coming in v0.15.0. We originally wanted to include Move in this release but it needs more testing so we pushed it back. Hang in there :)
• Much better thread sorting. Conversation threads on both the web view and client API use a new sorting mechanism which makes them way more readable. No longer will replies in a thread be scattered all over the place.
• Better HTTP signature support. We fixed a longstanding issue with including vs not including query parameters in signed GET requests. We now try (and accept) both methods of constructing signatures. Which leads to...
• Improved thread fetching. You'll see far fewer "orphaned" statuses in your timeline now, and you'll see more replies on statuses from other instances.
• Syntax highlighting for code blocks on the web UI. When you include a code block in your markdown now, and correctly indicate the language the code is written in, it will be syntax highlighted when rendered on your profile in the web UI. This requires javascript to be enabled in a visitor's web browser, but it's a progressive enhancement feature. Visitors to your profile with javascript turned off will just see the code block without syntax highlighting :)
• Improved "about this instance" page, with a link to the page in the nav bar. Previously the "about this instance" page was more or less hidden. We've now surfaced it better, so you can write all your terms and conditions and instance description stuff there. Relatedly....
• Parse instance descriptions and terms and conditions as markdown. Previously it was very difficult to properly edit these fields, because you had to read + write HTML to do so. Now they're parsed as markdown. This means you can more easily include things like blockquotes, lists, etc.
• Big refactor of HTML templates + CSS. We did a serious rework of HTML templates to fix indentation. Previously if you did "view source" on a GoToSocial profile page, you'd see a mess of sloppily-indented HTML. With this refactor, the HTML is now nicely indented and much more readable. We also did an accessibility pass and tested our HTML with various screen readers to try to make the web view a bit less annoying to navigate.
• First pass at a basic spam filtering system. In light of spam waves happening on the fediverse recently we took a crack at implementing a filter to drop messages identified as spam. This is still in the experimental stage, but it's included in this release so you can try it out already. See the docs for details.

Thanks for reading!

Hi everyone! We just made another security + bugfix release for #GoToSocial

github.com/superseriousbusines…

If you're running on v0.13.2 or below, you should update to this release as soon as you have the time. There are no database migrations or frontend file changes, so this should be fairly easy!

Similar to the v0.13.2 release, this one closes a couple gaps with regard to ensuring that remote accounts and statuses can't be imitated.

It also fixes a couple different bugs with regard to your instance trying to dereference accounts who've blocked you, or whose instances have blocked you, leading to less weird-looking behavior from the user's side :)

Oh, and as a nice side effect of the above changes, federation with Bookwyrm should work a bit better now too! 📖 🪱

If you're running on a main snapshot build, you should update to the latest code on main by either refreshing the Docker snapshot tag, or taking the latest binary snapshot bundle.

Now with that out of the way we can get on with working on features for 0.14.0 :P

Thanks for reading! Have a good Thursday!

Release v0.13.3 Spideriest Sloth 2: The re-slothening · superseriousbusiness/gotosocial

Hi everyone! This here's a security + bugfix release for GoToSocial! Similar to the v0.13.2 release, this one closes a couple gaps with regard to ensuring that models of remote Activities or Object...

^GitHub

Hi everyone!

We've just released a new version of #GoToSocial, v0.13.0 aka Spider Sloth!

You can get the release from here: github.com/superseriousbusines…

As usual, please read the migration notes carefully when upgrading to this version.

Thanks! Enjoy!

Highlights of this release:

• Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Question activity types. You can create, view, and vote in polls using your client of choice.
• Show unsupported media placeholders in incoming posts, where media could not be downloaded (temporarily or otherwise). No more dropped media on posts! You'll instead now get a link to the media on the originating instance, that you can click through in your (mobile) browser.
• Mute threads that you're being overwhelmed by. Notifications for replies, likes, and boosts in that thread will no longer be generated.
• Media cleanup scheduling. Previously media scheduling took place every night at 12am. With the new media scheduling settings in the config, you can customize the schedule to run it at different times and frequencies. docs.gotosocial.org/en/latest/…
• Support for setting instance language . You can use the new instance-languages setting to indicate one or more primary languages for your instance. docs.gotosocial.org/en/latest/…
• Support for language tags on posts. Language of posts is now correctly federated in and out of your instance. The language of posts is also shown on the web view of statuses and threads.
• Gather and expose prometheus format metrics. You can now expose a /metrics endpoint to allow a Prometheus instance to scrape metrics about Go runtime memory usage, http request and database metrics, and more. docs.gotosocial.org/en/latest/…

Release v0.13.0 Spider Sloth 🕷️ · superseriousbusiness/gotosocial

Spider Sloth, Spider Sloth, does whatever a .... sloth does? Release highlights Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Quest...

^GitHub

Hiya! It's a gloomy day so here's a little ray of sunshine:

We just tagged + pushed the second release candidate for 0.13.0 of GoToSocial!

This contains mostly fixes for pesky bugs from the first release candidate. You can get rc2 here:

github.com/superseriousbusines…

Note that on SQLite, when you start up your instance an analyze will run when you switch to this version. The analyze might take a good few minutes to run, depending on how large your SQLite database is, and how performant your system is. Please be patient and don't interrupt it, it's optimizing your database :)

As usual, if you find any bugs specific to this release candidate, please open them on our issue tracker.

Thanks for reading, and enjoy the release candidate!

#GoToSocial #Slothware

Issues · superseriousbusiness/gotosocial

Fast, fun, ActivityPub server, powered by Go. Contribute to superseriousbusiness/gotosocial development by creating an account on GitHub.

^GitHub

Happy Friday everyone! Hope you're staying warm!

To celebrate the weekend, here's the first release candidate (rc1) for #GoToSocial 0.13.0 Spider Sloth!

github.com/superseriousbusines…

As always, please read the migration notes carefully when updating. If you find any bugs in the release candidate, kindly let us know on Github!

Release highlights below the line.

• Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Question activity types. You can create, view, and vote in polls using your client of choice.
• Show unsupported media placeholders in incoming posts, where media could not be downloaded (temporarily or otherwise). No more dropped media on posts! You'll instead now get a link to the media on the originating instance, that you can click through in your (mobile) browser.
• Mute threads that you're being overwhelmed by. Notifications for replies, likes, and boosts in that thread will no longer be generated.
• Media cleanup scheduling. Previously media scheduling took place every night at 12am. With the new media scheduling settings in the config, you can customize the schedule to run it at different times and frequencies. docs.gotosocial.org/en/latest/…
• Support for setting instance languages . You can use the new instance-languages setting to indicate one or more primary languages for your instance. docs.gotosocial.org/en/latest/…
• Support for language tags on posts. Language of posts is now correctly federated in and out of your instance. The language of posts is also shown on the web view of statuses and threads.
• Gather and expose prometheus format metrics. You can now expose a /metrics endpoint to allow a Prometheus instance to scrape metrics about Go runtime memory usage, http request and database metrics, and more. docs.gotosocial.org/en/latest/…

Release v0.13.0-rc1 · superseriousbusiness/gotosocial

Well well well, look what the sloth dragged in... the first release candidate for v0.13.0, Spider Sloth. Release highlights Create, view, and vote in polls. It's been a while in the making but GoT...

^GitHub

documented how #GoToSocial formats Mentions when federating, and how it tries to parse incoming Mentions:

docs.gotosocial.org/en/latest/…

Bugfix release! ❌ 🐛

Here's #GoToSocial 0.12.1 Spaghettier Sloth:

github.com/superseriousbusines…

Notes for this release:

Hiya! This here is a bugfix release for 0.12.0 Spaghetti Sloth!

We fixed csv block/allowlist import/export in the settings panel, instance terms and conditions updating, and also a silly issue where you couldn't use the settings panel to update your profile if you didn't have custom CSS enabled on your instance (blame me, tobi, for all these shiny new frontend bugs).

For detailed release notes, instructions, and warnings, please follow the 0.12.0 release notes and just replace 0.12.0 with 0.12.1 throughout. Thanks! Enjoy!

Release v0.12.0 Spaghetti Sloth 🍝 · superseriousbusiness/gotosocial

Hello! Here's version 0.12.0 of GoToSocial, codename SPAGHETTI SLOTH 🍝 Release highlights This release brings initial support for different federation modes, starting with allowlist federation mode...

^GitHub

tobi here; here's an update on 0.12.0!

we had a few more yaks to shave than we realized, so we're still taking our time shaving them

this includes refactoring some of the settings panel code by introducing some typescript into the codebase where appropriate, to hopefully make future admin/settings panel changes a little easier to implement

we're also working on adding some initial support for polls and for processing incoming status edits -- these two features are surprisingly intertwined, with one another, so getting them implemented nicely involves a bit of juggling

so sit tight for a bit longer for 0.12.0 :)

if you're feeling daring and want to try the latest changes without waiting for a proper release, we have instructions right here for running from the latest snapshot build from main (at your own risk)

that's it from us for now! have a good monday!

#GoToSocial

GitHub - superseriousbusiness/gotosocial: Fast, fun, ActivityPub server, powered by Go.

Fast, fun, ActivityPub server, powered by Go. Contribute to superseriousbusiness/gotosocial development by creating an account on GitHub.

^GitHub

The #GoToSocial stats have really popped off in the past 2 months.

There's over 600 servers online! This is scary and exciting!

gotosocial.fediverse.observer/…

Please consider supporting us with €12/ year if you run as server, or use a server, or just wanna support us in general! (there are other donation options available)

opencollective.com/gotosocial

GoToSocial - Open Collective

Develops open source Fediverse/ActivityPub software

^{opencollective.com}

I keep seeing lots of people who are totally giddy about the #Fediverse, who are gushing over it, who want to promote it, who want it to spread.

And who want it to advance. To learn new abilities. To grow new features.

That's all fine and dandy.

But almost all of these people are still fully convinced that the Fediverse equals #Mastodon. And nothing else. At least not until Tumblr and P92 join the fray. Okay, maybe the #WordPress plug-in that's the talk of the town now that it has become official. Okay, maybe a few of them have also heard of #Pixelfed and/or #PeerTube because their makers are all over the Fediverse.

When these people are talking about the Fediverse, they mean Mastodon. And when they're thinking about the Fediverse, they're only thinking about Mastodon. Because that's all they know.

So these people want new cool features or even new cool use-cases in the Fediverse, stuff that Mastodon doesn't have. They want Mastodon to have it, or they want new projects to be launched that have these features.

If only they knew.

If only they knew that everything, literally everything they propose has already been done. Yes, in the Fediverse. In projects which are fully federated with Mastodon. Why don't they know? Because they've never heard of any of these projects, much less what they can do.

So they want "quote-tweets" in the Fediverse. Which means they want Mastodon to introduce them.

Tell you what: Mastodon is the only microblogging project in the Fediverse that doesn't have quotes. Not only will Eugen Rochko never introduce them, but all the other projects have them with Mastodon forks #GlitchSoc such as being the exception. #Pleroma has them. #Akkoma has them. #MissKey has them. #CalcKey has them. #FoundKey has them. #GoToSocial has them. The old heavyweights #Friendica and #Hubzilla have them, and so does Hubzilla's youngest decendant, the #Streams project. Et cetera.

You want "quote-tweets"? Switch to something that isn't Mastodon, and you've got "quote-tweets".

Or text formatting in posts like bold type, italics, underline, strikethrough, code blocks etc. Would be great if Mastodon had that, in spite of other people saying they don't want it.

Again: Pleroma already has it. Akkoma already has it. MissKey already has it. CalcKey already has it. FoundKey already hasit. GoToSocial already has it. Friendica already has it. Hubzilla already has it (look at this post at its source in a Web browser and weep). (streams) already has it. And so forth. This time, even Mastodon forks have it.

It has been done. It has been done many times. It has actually been done before Mastodon.

Next, long-form blog posting. We need something like #Medium in the Fediverse that isn't Medium itself. Mastodon's 500 characters are too few, and Twitter-like threads are inconvenient.

Except we already have that, too. #Plume and #WriteFreely are about as close to Medium as Mastodon is to Twitter, including clean and distraction-less layouts. Oh, and Hubzilla can do that, too.

By the way: Again, Mastodon is the only Fediverse project that can do microblogging that has a 500-character limit. Pleroma, Mastodon's oldest direct competitor, raised it to a default of 6,000. MissKey and its forks have 3,000 as a default. Friendica, Hubzilla and (streams) have character limits of "go ahead, drop your short story in one post in its entirety," so virtually none at all. And yes, Hubzilla has long-form writing on top of that.

Speaking of Hubzilla: Most recently, there has been the idea to uncouple one's online identity from a specific instance. Your online self should no longer be firmly tied to any one server exclusively. Now, this sounds so ambitious, it might just as well be science-fiction.

What if I told you that just this very thing already exists as well?

No, really. No, I'm not making this up. But you should know by now that I'm not.

Better yet: It was conceived as early as 2011. By the guy who launched Friendica in 2010. He invented a new principle named #NomadicIdentity and a new protocol named #Zot. In its early stages already, even with no technical implementation yet, Zot was more powerful than ActivityPub is today.

In 2012, Zot became reality as the basis of a Friendica fork which later became known as #RedMatrix and, upon its 1.0 stable release in late 2015, which is still prior to Mastodon's initial release, Hubzilla. Hubzilla is still being developed and improved, and it has a fledgling but growing "successor of a successor" named (streams) which offers nomadic identity, too.

Now, what does this nomadic identity even look like? Well, not only does it let you move your channel(s) around from instance to instance with ease and, unlike on Mastodon, with absolutely everything on it. No, it also lets you have your channel on multiple instances at once. Identical clones, automagically kept in sync in real-time, all with the same identity, the same content, the same connections.

Your identity is no longer strapped down to one instance. Not only that, but your channel, your posts, your content is no longer hosted on only one server. This means that if one instance with one of your clones goes down, you still have spares.

Okay, so how about community groups/forums? That'd be cool.

Well, for one, there's #Guppe. It's basically bolted on Mastodon, and in practice, it's centralised because there's only one instance. But it's impractical to use.

Besides, this is becoming a running gag here, Friendica, Hubzilla and (streams) have exactly this built-in and open for the rest of the Fediverse.

Better yet: There's also #Lemmy which amounts to a federated #Reddit or #HackerNews clone. So not only does Lemmy offer this, it specialises in it.

Hubzilla alone can provide Fediverse feature suggestions with "has been done" for years to come. Not to mention what else the Fediverse has to offer. Even if someone should want a free, non-commercial, decentralised, federated #GoodReads clone in the Fediverse, it has been done: #BookWyrm.

- Fediverse.Party - explore federated networks

Let's make social media free, federated and fun! Fediverse.Party is your guide into the world of decentralized, autonomous networks running on free open software on a myriad of servers across the world. No ads and no algorithms.

^{fediverse.party}