Skip to main content

Search

Items tagged with: GoToSocial


#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!


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.


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!


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:


Right, before I dig in too far, can anyone comment to the stability of #GoToSocial these days, as well as how well it's kept up with compatibility with the Mastodon API? Also, person number 389 here saying that it would be great to have a spreadsheet of all of the various fediverse software and how they're different from one another.


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


!Friendica Support
Hat hier schon mal die Kommunikation zwischen #Gotosocial und #Friendica getestet?
Ich habe hier von Gotosocial Nutzern die Info erhalten, das er/sie mein Profil bzw. mein Profilbild nicht angezeigt bekommt.
Wenn er dann aber mit #Mastodon oder #Calckey einen Kontakt hat - dann wäre das gar kein Problem.
Da ich das jetzt nicht nachvollziehen kann in Ermangelung einer Gotosocial Instanz

Ist hier etwas bekannt?


Hi everyone!

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

You can get the release from here: https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.0

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. https://docs.gotosocial.org/en/latest/admin/media_caching/#cleanup
  • Support for setting instance language . You can use the new instance-languages setting to indicate one or more primary languages for your instance. https://docs.gotosocial.org/en/latest/configuration/instance/
  • 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. https://docs.gotosocial.org/en/latest/advanced/metrics/


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:

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

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


To nevypadá špatně. Jede i na slabém stroji. Pro někoho kdo chce mít malou instanci super
#activitypub #gotosocial #fediverse
https://docs.gotosocial.org/en/latest/
https://github.com/superseriousbusiness/gotosocial


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!

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

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. https://docs.gotosocial.org/en/latest/admin/media_caching/#cleanup
  • Support for setting instance languages . You can use the new instance-languages setting to indicate one or more primary languages for your instance. https://docs.gotosocial.org/en/latest/configuration/instance/
  • 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. https://docs.gotosocial.org/en/latest/advanced/metrics/


Bugfix release! ❌ 🐛

Here's #GoToSocial 0.12.1 Spaghettier Sloth:

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

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!


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


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

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

https://gotosocial.fediverse.observer/stats

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)

https://opencollective.com/gotosocial


Re-inventing the federated wheel because you don't know that wheels exist


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.


Content warning: GoToSocial news, fundraising post, OpenCollective launch