Well, it’s a list of "well maintained/moderated servers
Any server that federates with threads, a product of Meta a company known for their low quality moderation and lack of ethics, is clearly not a well maintained/moderated one.
It’s not a new rule. The admin is just applying the sites rules as they are, instead of making exception for threads as many of the techbro admins that are getting their servers excluded have been doing.
I don’t have iOS, so I never used voyager. And to be honest, it’s been a lot since I used a mobile app to access Beehaw; I only do so through the web.
Now with the moving away from Lemmy to a different software confirmed, I’m waiting to see what the options are for the new platform and choose a new app from that.
Not only is PixelFed not a competitor in terms of users, but the dev is desperate to cooperate and welcome Meta to the Fediverse. So it doesn’t represent any kind of threat for the company’s goals, at least at the moment.
See how quick he was in defending meta after they came with the bug excuse and how quickly he’s adding threads to the fediverse datebase to the point that the clone of Zuckerberg’s account that cannot even fully interact yet is called “the most popular fediverse account”
I think part of the issue with Ello was that they sell themselves as non-corporative social media while maintaining two of the most important characteristics of corporative social media:
Centralisation and lack of federation
Being closed-source
The story would have gone completely different if they
Had made it open-source allowing users to contribute to the project, both as devs and through donations.
Added decentralisation and federation, allowing others to make their own Ello servers. This could have taken a lot of weight (financial and otherwise) from the developers/founders. Users cost money. Dividing the user base within different servers, pay by and moderated by different people means dividing the costs.
I would prefer if Beehaw remained federated, but, as it is, I understand that the options of software for a platform like Beehaw on the fediverse are lacking on many aspect and started something new requires time,knowledge, and money.
Last year hasn’t been a good year for me, to be fair. I’ve been having some health problems (luckily I’m on medical treatment and it’s nothing serious)
I don’t expect much from this year, but I hope to be able to do more things (and be once again active in the fediverse) now that my health issues are more controlled.
New year celebrations were alright. I expend it with the family.
Aren’t there ways to automatically scan the content of posts to detect csam and other disturbed content?
Because completely disallowing images isn’t the solution. For once, people can still share those things through links. And secondly, there are people who need images and the like to communicate.
A question about federation (if Beehaw decides to go the non-federated software to federated path), is ActivityPub the best option to re-federate the new Beehaw (if it happens)? It’s too big and maybe you could reinstate federation with a different protocol and then, if it all goes well, incorporate ActivityPub.
Basically, Lemmy communities and Kbin magazines are federated as groups to the micro and macroblogging fediverse. People in friendica, mastodon or Firefish can interact with Lemmy and kbin by mentioning a community/magazine in their posts and following them the way they do with other types of federated groups (like guppe, chirp, friendica forums, etc)
Pixelfed didn’t have federates group support, meaning that its federation with the threadiverse was bad, not to say practically non-existent. Supporting federated groups and even having its own type of group will allow people on pixelfed to interact with Lemmy and Kbin the way other fediverse software do: following them and tagging the community/magazine handle in posts.
short summary: It means better federation between Pixelfed, and Lemmy and Kbin.