@spiderrobotpig right now we're trying to fix the back end issues which render instances broken when they get too big, and improve the new user experience and create a landing page. This isn't anti-harassment but it is important and urgent.
After that we want to implement thread notification muting to counter mass-tagging/dragnet harassment, and there's been talks of "Block heatmaps" to help admins identify trouble users. like if a user is blocked by tons of ppl fast I get pinged
@spiderrobotpig because the "default" is to assume someone is a cishet white male it's easy to assume that no marginalized groups are involved but the Mastodon development team is full of trans women, gay people, and disabled people. Also lotsa cis women now too.
it's still majority white... but past that we are diverse in other ways. It's an open source project and anyone can help out. Of course uncompensated labor is not ideal though... but it's not in our means to fix that rn.
okay look
#mastodev, there needs to be a brainstorm on something:
a lot of users are concerned about cross-instance users using their username and impersonating them
what would be a good and userfriendly way to fix this?
gnu social doesn't even have a fix for this yet, it seems, so...
You know, there's one solution that hasn't been brought up in relation to impersonation that'd work the best because we're already doing it.
Moderate servers so that people intentionally impersonating other users are not allowed, and then block other servers that actively refuse to do this.
My Harry Potter federation explainer:
Your instance is your House at Hogwarts. The local timeline is a common room shared with the other wizards in your instance.
The federated timeline is the dining hall, your instance + people from other instances, but not the whole wizarding world.
Then the dark Memelord rises & Shitposter.club* dogpiles the Hufflepuffs & @[email protected] has to die & resurrect in an overt Christ analogy to save Mastodon.
It kind of got away from me at the end.