It should really be: "Threads just enabled bi-directional commented with part of the fediverse" as their implementation of ActivityPub seems to focus mainly on compatibility with #Mastodon. Threads' ActivityPub implementation is broken enough that it will not federate with instances like mine that run #GoToSocial.
My biggest concern is likely speed / having something lightweight. Next come ease of administration (likely a single person instance), and having some moderation features.
I didn't know how much I missed them since I went from #Mastodon to #GoToSocial and previous versions of GoToSocial didn't have filters implemented yet.
Now that they have been added filters to GoToSocial v0.16.0, it's so nice to be able to filter out things from my feed. Thank you GoToSocial team for all your hard work.
When does user stats start populating in #GoToSocial v0.16.0? This is the one feature I've been looking forward to in this release. Right now I'm looking and it seems post counts are showing up, but follower and following counts aren't yet. #GoToSocialAdmin#fediverse
Hi nerds! We've just released #GoToSocial version 0.16.0 Snappy Sloth into the wild. Look at it go! Climbing trees and all sorts, covered in algae, and #pooping once a week.
Thanks to everyone who helped us comb the bugs out of its fur during the release candidate process. We hope the protein you gained from eating the bugs was reward enough.
As usual, when updating to this version (which you really should, because it's quite good), please read the release notes carefully, particularly the database migration notes; and make sure you don't interrupt the database migrations.
Ta!
Highlights of this release (nothing new since 0.16.0-rc1, just reiterating):
Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
Documentation here: https://docs.gotosocial.org/en/latest/admin/signups/
Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
Documentation here: https://docs.gotosocial.org/en/latest/user_guide/search/
Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.
For adventurous instance admins, please read the release + migration notes very carefully when updating to this release, paying particular attention to the database migrations section.
Here are the release highlights:
Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
Documentation here: https://docs.gotosocial.org/en/latest/admin/signups/
Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
Documentation here: https://docs.gotosocial.org/en/latest/user_guide/search/
Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.
Are you interested in accessibility on Mastodon? Are you blind or do you know someone who is blind and wants to use Mastodon?
There is a Mastodon-compatible accessibility app for Windows and Mac called TweeseCake which is designed for blind and sight-impaired people. You can find out more on its website at https://tweesecake.app
You can follow the developers of TweeseCake at @app
Is there a free #Mastodon / #Akkoma / #gotosocial host that would let me create accounts in bulk and run some automated feeds through them without considering it abuse?
Every morning, an instance administrator wakes up knowing they need to keep the infrastructure running smoothly for their users, ensuring a good and free social experience.
Every morning, a Fediverse user wakes up knowing they will find many people eager to socialize and interact, who strive to keep the Internet a place for the free exchange of ideas and opinions, away from the dynamics of closed protocols and Big Tech monetization.
It doesn't matter if you are a server administrator or a Fediverse user, thank you for being here and for contributing every day with your efforts to keep the Internet a free place.
Quote Posts, being able to limit them, and possibly being able to limit replies, is coming to Fediverse soon enough.
I am a bit worried about these features for all the same reasons that others are, as well.
However, I have another worry that I haven't seen talked about yet, because it's a limited experience so far.
Threads added the ability to limit Quote Posts yesterday and I've already played around with it to see how it works.
I'm worried about Mastodon using the same kind of way to limit Quote Posts as Threads.
Currently, the way Threads does Quote Posts, is that whenever you post a link to a post, it automatically turns into a quote post. Therefore, when you limit them, nobody can even link your post on the site at all.
That's currently how Threads Quote Post limiting works and that really sucks if that severe limitation would come to the wider Fediverse.
My worries might be unfounded. This might be not at all how Mastodon will be doing it and everything will be fine.
Ryan made a pretty good point around the 16 minute mark about how Threads wasn't told to make their federation "opt-in" from the Fediverse side and that people feel differently about bridges for some reason.
Even though, they're the same thing, in most ways. 2/?
So, at the 29 minute mark, Ryan talks about how Mastodon's search discoverability feature is currently opt-in and there's only 5-6% of people currently opting-in. That's a wild statistic!😬 3/?
This video is SO good! Anyone who is interested in Fediverse nuances and the issues we've been debating for months now, should definitely watch this video! 4/?
I haven't done that in A LONG TIME. However, there's been LOTS happening and I'm very excited for the future of the platform, right now.
I am obviously still a little cynical when it comes to corporations and their intentions with Fedi, though.
If I have time, (and if I feel good enough. Anxiety is a bitch) I'll do a writing session and detail my thoughts, reasonings, and experiences with this social movement so far.
I'll also be detailing the nuances of each cross-platform integration I have firsthand experience with.
Let me know if this is a type of blog post would be interesting or intriguing to you and it might help me with motivation to pull it off. I don't want to "yell into the void". Especially with something I have so much passion for, and will take some time to complete.
If your profile and posts are set to "public" and you can read this very post, you should have no sense of "privacy" here on Fedi. That means ANYONE can reply.
There's 20,000+ instances and new ones every day, there's NO WAY to tell who is accessing your posts or what they're doing with them.
Fediverse is not some kinda "bastion for privacy" nor is there any sort of "consent" required to see your posts if they are public.
The only way you can be 100% sure that your followers are the only ones that directly see your posts is to make your profile and posts private. Even then, screenshots exist.
Remember, you're on the internet. Once you post it, it's probably not going away. This is true everywhere.
I am used to simple things running on Docker (Jellyfin, Nextcloud, etc.) I am looking at running my own personal Mastodon instance (maybe share it with a few friends and family), but I like using Docker. Looking at install guides, the steps required seem to be much harder than just editing docker-compose.yml and running the...
Instead of the full-blown Mastodon, you should also look at #GoToSocial which is compatible and pretty light-weight. (Doesn’t come with a web UI, so you need to use client apps.)
If there were ever a single post that truly shows how running a Fedi instance is, that I could boost to the moon, it's this one.
People still somehow think that Fedi is "opt-in" or "privacy focused" or even "community focused". None of these things are true and I wish more people understood.
It's not a BAD thing, per se. I like it, personally. I choose who I want to interact with by blocking those instances I DON'T want to interact with, but it's OPEN BY DEFAULT is something some people can't grasp.😬
Some people get replies and just do not engage at all....
Like, what is the point of posting to social media if you're not even gonna be SOCIAL?!?🤦♂️
Especially Fedi, cause it's not like we have some dumb ad service that pays you for views...You ain't making money here unless you're posting off-platform links to buy stuff.
I just don't get it. It's social media. Not "shout to the void and ignore everyone" media.🙄
Well, I have deleted the Threads app. They don't seem interested in integrating in good faith, unfortunately. Therefore I don't see any point in advocating for them further.
Federate with them if you wish, but my first hand experience with their dev team has been completely in bad faith on their part...🤦♂️
Every now and then while browsing the Federated timeline, I'll come across that dumb troll who says something like "Fediverse SUCKS! There's nobody here!!!"
All I can think in that moment is, "oh yeah? Then who the fuck are you and why are you on my timeline?!?!"
🤦♂️people are so dumb. Don't post on a platform and complain about it unless you're trying to make the platform better.
Is it that difficult to run Mastodon over Docker?
I am used to simple things running on Docker (Jellyfin, Nextcloud, etc.) I am looking at running my own personal Mastodon instance (maybe share it with a few friends and family), but I like using Docker. Looking at install guides, the steps required seem to be much harder than just editing docker-compose.yml and running the...