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:
@andreclaassen das #fediverse ist so voller verschiedener sachen, #firefish#gotosocial#castopod da kann man soviel ausprobieren von motivierten leuten programmiertes, da hab ich persoenlich gar keinen bedarf zu schauen, was die milliardaere des planetens so programmieren lassen.
wir sind zwar nicht mehr, aber vielleicht genug ;)
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.
I'm now running a test instance of #gotosocial as my new self hosted Fedihome.
I'd appreciate if my followers could just follow @mike as well as this account. That way I can ease the transition and hopefully avoid too much disruption.
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).
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
Feditext beta users: today's version 1.7.2 (build 83) fixes reporting posts when using a GotoSocial server, adds support for instance rules on GtS 0.12 and up, and fixes a rare visual bug with reporting on all platforms. this build is recommended for GtS users; if you use something else, you don't need to upgrade immediately.
thanks to tobi from #gotosocial I can finally see profile pictures for a lot of users on my feed... i'm so happy! It was my fault they broke in the first place
(I know you scan that hashtag sometimes so thanks again!!)
For those, like me, who want their own space here and prefer self-hosting, I suggest considering snac2. I'm having a great experience with it, and it's easy to install and configure.
Running the latest GoToSocial instance in rootless podman for a few days now.
So far, I am mostly pleased. There is a lot missing features (it's still alpha, after all), there was one hiccup even - for an hour, it was not syncing anything from fedi and I still didn't find any reason why, had to restart it - let's see if it happens again), but it's really lighweight, updates are quick and easy (I help to manage a mastodon instance and update process is hellish in comparison) and the community around it is also working very fast to get it to beta. Definitely worth supporting.
It doesn't matter if you are new to the #fediverse or if you have been here forever, it's always good to keep in mind that (a) what server you pick, and (b) what software that server runs, matter.
I should admit am fairly new at this. I created my first fediverse account only a year ago. It was a #mastodon server with about 8,000 users. And while it "worked" there was something missing from the experience.
While researching the idea of hosting my own server, I discovered #FireFish which in turn led to discovering #IceShrimp. It's hard to describe how much better the experience is with IceShrimp.
The #UI is just so much better, and the feature set way more robust. The way it handles replies, the ability to quote, to use multiple emojis, etc.
If you have friends or family thinking about joining the Fediverse or are feeling unimpressed with your mastodon experience, I highly recommend getting an account running IceShrimp or other similar software.
Probably also worth mentioning that I also looked at using a #Wordpress integration and #Hubzilla#GoToSocial#Pleroma#Humhub and #Streams. I found them to be clunky; reminding me of how email was in the early 90s.
If the fediverse is going to thrive, then it needs to make a good first impression. Moving beyond mastodon is a good step in the right direction.
0.13.1 Spiderier Sloth fixes a couple small issues with poll vote counts and poll expiry, and an issue where domain blocks were sometimes not being properly enforced when deeper- and higher-level domain blocks were used in combination (eg., when combining blocks for say example.org, bad.example.org, also-bad.example.org).
There are no database migrations or config file changes on this one, so upgrading from 0.13.0 should be very simple :)
Well, that might be it for my #GoToSocial server @bitslag ... highlights the importance of not putting trust in free subdomains haha oh well it was just a test anyway, but yeah I wish the fediverse supported changing domains better and was less reliant on domains and usernames to begin with ... somehow ... maybe with an onion routing type system or something. I dunno! Anyway. That might be it for now for GoToSocial. Farewell!
I kept my #GoToSocial server going for about four months. I just killed it. It was in the Oracle Cloud, and the upgrade of #AlmaLinux from 9.2 to 9.3 was taking a long time. I thought it was hanging, and I hit ctrl-c. That stopped a "scriptlet." I reran the upgrade, which said it completed. I should have know then to remove the new kernel. I rebooted, and that was it.
I hadn't yet set up backups for this server because I considered it experimental.
I was able to pause GRUB with Oracle Cloud's serial console and boot into an old kernel.
Barbaric as hell. That's my review. I removed the latest kernel and then upgraded it. I'm not sure it will work, so I'm not rebooting for now. I'll wait for a new kernel, upgrade that and THEN reboot.
So for now my #GoToSocial server is back among the living.
Time to figure out a backup plan. I've already started. In my mind, that is.