Profile for gotosocial

Header for gotosocial
Avatar for gotosocial
Display name
GoToSocial
Username
@gotosocial@superseriousbusiness.org

About gotosocial

Bio

The official account for GoToSocial news, updates, release announcements, and so on!

GoToSocial is an open-source, ActivityPub compatible, federated social media server. It's easy to install, lightweight, and runs quite well on small servers πŸ¦₯

GoToSocial is still alpha software. Your support is appreciated as we fix bugs, add features, and move towards beta ❀️

This is not a support account! Support questions addressed to this account will go unanswered. For support please see the links!

Stats

Joined
Posts
896
Followed by
2832
Following
23

Pinned posts

jump to recent

Hey! We forgot to post about this earlier because LIFE keeps happening, but we updated our roadmap document:

https://github.com/superseriousbusiness/gotosocial/blob/main/ROADMAP.md

Check it out if you wanna get a feel for the order in which we'll likely implement things.

Also please note that just because something is not on the roadmap, doesn't mean we won't implement it! The things listed there are just the main things we wanna do (and are getting paid for by our NLnet grant), but we are always squeezing in little fixes + features here and there :)

Open thread at this post

Our stance on the 'transgender question' is that it's not a question. Trans rights are human rights. Trans lives are precious. Trans people are beautiful, and endlessly worthy of love, respect, and care. That is an unequivocal, simple truth.

Open thread at this post

Did you know that the GoToSocial API is documented using Swagger / OpenAPI?

Well, it is :) Check it out: https://docs.gotosocial.org/en/latest/api/swagger/ (javascript required)

We do our best to keep our API documentation up to date, to make life easier for people who want to write client applications. We’ve still got a few things missing from the docs, but it’s mostly there, with examples too! :)

Open thread at this post

GoToSocial is getting a ton of attention lately. So I just wanna reiterate that if you're using GtS, you're using alpha software that has many features not yet implemented, and is chocka with bugs. We're quite proud of how the alpha development phase is going so far, but we make no guarantees whatsoever about stability, data loss, performance, etc etc. You use alpha software at your own risk.

There are many things you can do in Mastodon (and mastodon clients) which will 404 on GtS because they're simply not implemented yet. We are aware of what these are, and they're documented both in the roadmap document and in the faq in the docs. We're currently revising the roadmap document for the next year, so we'll have an updated version to share soon (tm).

Opening issues about features that we've yet to implement will not get them finished any faster: if anything, it will be slower because we then have to deal with answering issues. It is especially unwelcome to comment 'where is x feature' on an unrelated PR / issue. The cake is in the oven and it's not ready to eat yet, so stop asking if you can stick your fingers in it.

The team managing PRs and development and admin and planning and triage and releases and offering help in the help channels is 4 people, only one of whom (tobi) currently works full time on the project. While we're very open to PRs, feedback, and collaboration, we are also essentially just weirdos who like to be left alone to tinker with code, cuddle cats and dogs, and listen to music. This is home grown, open source software which started as a hobby project. Not a big company with support staff. Please be mindful of this when you're asking for support!

If you want to recommend GoToSocial to people, thank you, your enthusiasm is very appreciated! But please accompany your recommendation with the provisos I mentioned here, so that people's expectations are set appropriately. We don't want anyone to come to the software expecting miracles and ending up disappointed.

Phew, thank you for reading ❀️!

Open thread at this post

Recent posts

Good morning! What are your favorite preset themes in #GoToSocial 0.15.0? (multiple choice poll)

Multiple-choice poll closed , 128 votes total
  • Option 1, Light blurple πŸ’œ
    7.81% , 10 votes
  • Option 2, Dark blurple πŸ†
    19.53% , 25 votes
  • Option 3, Sunset πŸŒ‡
    10.16% , 13 votes
  • Option 4, Midnight trip 😎
    10.16% , 13 votes
  • Option 5, Soft 🌸
    3.91% , 5 votes
  • Option 6, I like the default / haven't tried the themes yet.
    48.44% , 62 votes
Open thread at this post

Hello sportsfans!

The proper release of #GoToSocial v0.15.0 Shagadelic Sloth has emerged blinking into the sun, fresh from the release candidate process :) One of our funkiest releases ever, since it contains some beautiful new themes you can try out (see screenshots).

You can get the release here:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.15.0

As always, please read the migration notes carefully! This release contains important database migrations that you should not interrupt!

Highlights of this release:

Open thread at this post

Hey nerds! 🌸

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

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.15.0-rc1

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

Release highlights

Open thread at this post

Another day another #GoToSocial bugfix release 😎

We fixed a bug present in v0.14.0 and v0.14.1 that was causing 404 errors sometimes when viewing an account or its statuses, if that account had moved at some point.

You can get v0.14.2 from here:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.14.2


No db migrations or config file changes between v0.14.1 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.2 throughout.

Open thread at this post

#GoToSocial bugfix release v0.14.1!

πŸ‘’
πŸ›

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.14.1

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 https://github.com/superseriousbusiness/gotosocial/issues/2728).

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!

Open thread at this post

Hi everyone!

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

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.14.0

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.
Open thread at this post

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

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.14.0-rc2

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!

Open thread at this post

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

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.3

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! :under_construction:

Open thread at this post

Hello hello! We just made a bugfix/security release of GoToSocial, v0.13.2.

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.2

Background

After Mastodon announced some vulnerabilities last week we looked through equivalent parts of our own code to make sure GtS isn't vulnerable in the same way.

Good news

We didn't find anything that would allow anyone to take over an account, or to post statuses or do updates as someone else: we check Create and Update activities carefully.

Bad news

We did find some areas where remote accounts could, with persistence and custom software, make a nuisance of themselves by pretending to be other accounts and sending fakes of a subset of activities such as Likes, Blocks, Follows, Announces (boosts), and Undo's of those things.

The above is not really easy to do, and we don't have any evidence that anyone's actually done it, but hey, now it's fixed just in case.

So, if you're running v0.13.1 or below, we recommend updating to v0.13.2 using the link above. The release doesn't contain any changes to the config file or templates or anything, so it should be a quick and easy update.

If you're running on main/snapshot: we recommend updating your snapshot to the latest code on main, which includes the fix. You can get the latest snapshot binary build from here or, for docker, update your docker image to the latest snapshot tag. Depending on how far back in commits you were before this release, there may be config file changes or other things, but likely nothing breaking.

As always, thanks for reading, and enjoy your week!

Open thread at this post

We're well on the way to #GoToSocial 0.14.0 release candidate 1!

Based on the sheer amount of fixes and improvements included, 0.14.0 will probably be the biggest release we've done so far :gtspat:

It will also (probably, unless something goes wrong) be the first GoToSocial release to include support for the Move activity, which will let you migrate an existing account to or from a GoToSocial instance, while keeping your followers and following relationships intact :) We waited a long time to write this functionality because we wanted to make sure GoToSocial was in a decent state before people start migrating accounts to it.

So, very exciting! If all goes well, expect more news on the first release candidate in a couple weeks (we're still fixing some bugs, as always).

Open thread at this post