So the first thing that I want to make clear is that Mastodon has a history of being inhospitable to marginalized users. This history is born out, as I’ve learned, through the marginalization and eventual shuttering of instances of color, of instances that were dedicated to hosting and supporting sex workers, of harassment of disabled users and so on. So Mastodon– while its federated model was premised on, well, the activity protocol, if I understand the history correctly– it was built in some ways to produce affordances that would avoid the kinds of harassment on Twitter. Things like quote tweet pile ons, things like other kinds of usage of the quote tweet or the comment or the reply feature to do violence. What that hasn’t done is prevented the violence. In fact, it’s given the kinds of bad actors who would do violence an opportunity to say, adjust to the new affordances because it’s not simply identities that are enabled by means of a digital environment, it is oppression that is enabled by means of a digital environment. So the oppression that one experiences on a platform like Mastodon will necessarily be different than the oppression that one experiences on a platform like Twitter, because of the different affordances of the platform.
I’m recommending to read the entire article of course, but this specific paragraph reminded me of an idea I had, to let instances subscribe to other instances’ block lists… With an option to sort the blocks by category, and to display followers-only comments? @BonfireBuilders #bonfire_feedback