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.
Latest #FOSSAcademic post: Researching the fediverse from the perspective of individual or instances. In which I draw on an article Christina Dunbar-Hester to talk about researchers' perspectives on the #fediverse, including my own.
ini adalah instance yanfg dibuat untuk tujuan uji coba. Siang tadi ane mendapatkan akses VPS dari provider dataideas dengan spesifikasi basic yang ane install #openbsd 7.5 sebagai OSnya.
Tujuan pembuatan VPS ini adalah untuk belajar dan ujicoba openbsd, nantinya jika sukses besar kemungkinan ane akan migrasi dari vultr (#freebsd)) ke VPS ini.
akun utama ane masih pakai #gotosocial di @poes dan ane belum ada rencana untuk pindahan ke instance lain meski sekarang gts sudah support perpindahan akun.
man man man ist das Anstrengend mit jemanden aus dem "Mastodon-Netzerk" zu diskutieren, der davon überzeugt ist, das mastodon die besseren Features hat als alle anderen Fediverse Dienste.
Ich frage mich nur, was soll das sein?
Die Software, die die BenutzerInnen am meisten einschränkt, soll also die bessere sein?
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.
Hello again #Fediverse, I may need your #fedihelp. So, here's a list of the Fediverse software I'm about to make temporary accounts for to test all the features and differences:
So, did I miss anything noteworthy? Does anyone have any tips or recommendations before I choose a server for any one of these? I'll probably be going for the most popular server on each for improved federation and maintenance.
Note: I'm using #Sharkey right now and Misskey forks are already overrepresented, so that's why it's not included.
Which may be a feature as far as most GTS and Snac users are concerned!
But I do want Threads to technically be able to federate with most/all other software that uses #ActivityPub, so it can be user/admin choice whether to accept connections from the giant instance...and more importantly, to cut down on the risks of vendor lock-in and EEE.
And I hope more compatible systems will cut down on the "OK, my software federates with itself and Mastodon, I'm done" problem. In some cases there may be bugs on the smaller project's side, and fixing them might also fix issues talking to other small projects.
If Facebook had an issue tracker for threads, someone could open an issue there. If threads was an open source project, we could look at the code and immediately know what's up, but... 🤷
#GotoSocial does not list ‘unlisted’ posts on your profile page when loaded in the browser … without authentication.
This may not be new to some of you, but I just realised how big of a deal that is. It means that it kinda operates like local-only posts for randos, in that they aren’t viewable by anyone who isn’t your “friend”.
i’m sure there is more to it than just that, but the brain is foggy today … and … come on … that is huge.
i need to focus on learning #go as soon as i get back… the more time i spend with it, the more i am in-love with it and i wanna help the team… i wanna feel useful.
How do you balance between a wide range of content and massive following (I'm at > 800) and handpicked timeline?
I know there are lists and there are relayServers (I'm operating a #GoToSocial instancen), but I still miss a lot of posts in the flood called timeline.
@st3fan I'm also running my #GoToSocial instance.
I follow hashtags via https://relay.fedi.buzz/ on an alt account so it populates my federated timeline with stuff I'm interested in. You can now either search for hashtags or create tabs on your main account.
#Fedibuzz relays can be followed like normal users, no relay support is needed. Example: @tag