Fore some times, mastodon has been unsafe for black and other minorities users, the peoples impacted by this have been complaining about it openly, emphasizing the lack of good moderation tools to make instances safer. The s on the dev team and userbase however have essentially plugged their ears and refused to listen, and instead engaged in bad faith, tone policing, minimizing racism, dismissing the testimony of black users, and telling them to “curate their experience better” with filters and blocks (even though a big part of the complaint is that this doesn’t work).
Seeing this, some black peoples who have been complaining about racism on mastodon and the lack of security features to deal with it have taken things in their own hands and made a fork of Mastodon named Awujo.
What kind of features are they proposing against the cracker hordes?
Implement better safety tools and expand the moderation experience Align the front-end experience with modern accessibility standards Reduce technical bloat to increase performance and stability Simplify setup and maintenance Define a transparent code contribution process Create a stable pathway for current Mastodon instances to migrate to Awujo
from A Case for Community
It’s a bit vague right now tbh, but it was launched pretty much today so we should give it time and see how it goes I guess.
This sounds vague of course, let’s see how it develops. Implementing better moderation tools shouldn’t be that hard. Reducing technical bloat sounds not that easy, it needs time. Probably a lot of refactoring will be done, if an increase in performance is expected. I am looking forward.
I am not familiar with mastodon but it probably also don’t have a way to add plugins or similar things. If the developers don’t want to add more moderation tools, than I would also just fork it. But isn’t it to much work regarding the optimisations that have to be applied? I mean, it does sound like that the code basis will start to differ fast from mastodon.
And why didn’t the mastodon developers want to implement these tools? I would understand, if there were technical reasons for it. I know from myself, that applying some changes may may also be not easy to apply, because the software was designed in a specific way (Or just a result of technical debt). But they just didn’t want to do it?
Looking into ActivityPub’s origins, I found this interesting: https://en.wikipedia.org/wiki/ActivityPub#Project_status
Lead author Christine Lemmer-Webber notes that the team predominantly identified as queer, which led to features that help users and administrators protect against “undesired interaction.” She also notes that the team authoring ActivityPub had no corporate participation.
This is a very welcome idea, and really hope it takes off. I use Mastodon fairly regularly, and lack of basic features like being able to limit who can reply to your posts is simply mind boggling.