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.
If an actor provides an outbox URL, but not an inbox URL, it means that it cannot receive Follow activities and it can not push content to the followers. In such cases, the follower's server should switch to periodic polling like RSS.
This will enable statically-built blogs ( #jekyll#hugo etc) to appear in Mastodon network.
Having second thoughts about my self-hosted #Mastodon instance, it’s just too much of a resource hog for a single user / small instance on a 4 core / 4G vServer if you want to run other stuff (#writefreely is live, #pixelfed to be installed!) as well. On the other hand it is very nice that the software is stable, reliable and well designed. So either I need to move to a bigger server or decommission my self-hosted profile and look into other options for micro / macro blogging self-hosting again. I did like #gotosocial but the current version doesn’t install on my #yunohost properly. Tried #Akkoma and #Pleroma - weren’t my thing, can’t get over the design. I do like #Friendica and its possibilities but it is a bit clunky at times and I have some doubts if protocols other than the quasi standard #ActivityPub have much of a main stream future which kinda could make the additional Friendica features a little islandish. Same applies to #Hubzilla which I only start testing. Leaves #Misskey and #Calckey which could be good options but not sure about the reliability and gameplan there, I don’t want to tinker every night on my server so #Calckey probably need to become a little more stable first, #Misskey seems to have no current version on YunoHost, so need to explore other install options… Any thoughts very welcome! @fediversenews@fediversede
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.
When someone asks about options for servers or clients I have a habit of tagging recommendations, and when there is not an account for the thing, I have to stop and search for a dev or find a website address to link to etc.
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.
I am working on spinning up a #GoToSocial (https://gotosocial.org/) instance that I am calling "Wisconsin Rocks" (I knew that my next instance had to be Wisconsin-themed). It works interchangably with #Mastodon, #Pixelfed, #Kbin, etc.
I have room for 10 users at the moment. Want to try it out? Give me a holler.
Are there any apps that use the #MastodonAPI that let you look at a list of your follows and add them to specific #lists as you go down the line, without opening each profile one at a time?
I'm trying to set up lists on my #GoToSocial instance now that it supports them, but I'm already following enough people over there that it's going to be a pain to either open all the profiles one by one or keep another window open so I can search for them one by one.
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?
Mastodon is hard to self-host, which leads to too few instances with open registrations. Gargron's solution is to redirect everyone on his one million users server.
At the moment the 419 instances having signed the #FediPact have 387,191 users, i.e. 4% of the total number of users and 27% of the number of monthly active users (MAU) (I give both numbers because we can expect these users to be more committed to the fediverse, so more active, than lingering mastodon.social accounts)
I have to admit that #Elk (@elk) is a pretty neat #Mastodon client if you're looking for a Twitter-like experience.
Feels very snappy and has all the feature I need. A few glitches with regards to auto-completion of tags and accounts, but I'm confident that the developers will fix those before the first non-alpha release.
Maybe #GoToSocial (@gotosocial) are a good combination for self-hosting. 🤔
does anyone know of any good fedi front end clients that are tailored towards long form blog posts? i want to turn todiy into a multi media platform, and not just microblogging, but i don't wanna have to run a separate server/subdomain for every format! I think i like the idea of using #GoToSocial as a backend because it seems pretty flexible! i dont want my users to need a bazillion accounts lol. Im looking at #writefreely , and it would be awesome to use its front end somehow. #fediadmin
Whoa check it out I got #GoToSocial going on the Raspi Zero 2 W. Gonna try logging in and following a few people, but I dunno if I'll keep it for very long. https://gotosocial.org
#TIL If your #GoToSocial fails to load avatars and the like it might happen that you need to add the respective file storage domain to your domain allowlist.
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
I setup a #GoToSocial instance at home, and it’s been a great learning experience. Reverse proxies, SSL, S3 buckets, caching and firewalls. Still lots to do!
It’s also interesting to watch the incoming fediverse traffic. Admins aren’t joking when they say ActivityPub is chatty. 😅 I’m only following maybe 12 people and it’s fairly constant.