These days, everyone hates big tech, and that’s often for very good reasons. You shouldn’t trust giant centralized companies that have collected a ridiculous amount of data on you. There are few re…
Not as dangerous as the hate trans people face every single day from the government, from media and from society at large.
Not really comparable to ethnic\religious\racial hate anywhere in the civilized world.
OK, I seem to answer lots of your comments not touching the actual core of the subject.
See, “per user” moderation is good because everybody’s idea of bigotry is subjective. Bad because it’s reactive, as you said, which means it takes effort from the user.
“Per community” is sometimes acceptable, though it always gets ugly over time. I’ve been a forum mod from time to time in the late 00s, I know what I’m talking about. If you can believe me, I stop being unhinged when handed opportunity to ban people.
“Per instance” is bullshit.
See, this has already been solved for email with client-side spam filters.
Or, with social media, you can in theory have kill-lists (for users and everything they post, or for separate posts), and subscribe to those. So, just like you want, somebody bans a user and everybody subscribed to that kill-list stops seeing them. No effort required, and without compromising others’ freedom to read.
I’ve been building and developing communities, queer and otherwise for decades. I’m also trans, and live it first hand.
The per user approach puts a cost on each and every user, and that cost can sometimes be too much for vulnerable folk dealing with harassment. Blocking the bigot with a throw away account after being exposed to the bigotry is pointless, because the account was going to be abandoned anyway, and you’ve already been exposed to the raw hate.
It makes it impossible to just have fun and enjoy your social media experience when you’re always waiting for the next bigot to drop it.
Instance level blocking resolves a lot of that.
Your theory of what will work just doesn’t cut it for many vulnerable folk, and it’s not going to start cutting it just because you want to debate the topic.
The per user approach puts a cost on each and every user,
I’ve described how it doesn’t.
Blocking the bigot with a throw away account after being exposed to the bigotry is pointless, because the account was going to be abandoned anyway, and you’ve already been exposed to the raw hate.
Which doesn’t change anything as compared to instance-wide or community-wide moderation. And if you mean that you only want to see approved accounts, that can be done without instance-wide or community-wide moderation too just as well.
Instance level blocking resolves a lot of that.
Nothing fundamentally prevents you from ignoring a whole instance. Or, from what I described with subscribing to kill-lists, that instance being blocked as a whole in that kill-list.
You people have gotten so used to commercial bullshit that you don’t realize how much can be done with simple things.
Your theory of what will work just doesn’t cut it for many vulnerable folk, and it’s not going to start cutting it just because you want to debate the topic.
It obviously does, because what I’ve described works exactly the same for the user, except for them having a choice.
Nothing fundamentally prevents you from ignoring a whole instance.
The issue is that users aren’t “instance based” in the same way they are on the fediverse. On the fediverse, instances are communities of like minded folk, so all of the bigots hang out in bigot friendly instances, which I simply defederate from. If they join non bigot friendly instances, they get removed
On Bluesky, bigots don’t belong to a particular instance. They just pop up with throw away accounts and have to be dealt with, one by one.
You people have gotten so used to commercial bullshit that you don’t realize how much can be done with simple things.
I’ve been on the fediverse longer than you my friend. I don’t use centralised social media of any type.
The issue isn’t that I “don’t realise”, it’s that what I want from a social media platform isn’t something that Bluesky offers. You want different things to me. Arguing at me as if you can make me want the same things as you is a waste of both of our times.
Bluesky doesn’t give me what I need, and it’s ultimately that simple
They just pop up with throw away accounts and have to be dealt with, one by one.
So a person to the kill-list of which you are subscribed does that, playing the role of a mod. There may be a few such people with their kill-lists, united by logical OR. You don’t have to do anything.
It’s just a better solution for what you claim to want.
Just say honestly that you want to ban some people in bunches and feel that it’s your bunch doing it and not you alone.
So a person to the kill-list of which you are subscribed does that, playing the role of a mod
Yep. After the troll has trolled.
It’s reactive moderation, which leads to a shit experience for vulnerable people if that’s how the majority of moderation needs are met.
Because fediverse accounts are instance based, and instances have their own rules and communities, bigots tend to cluster with other bigots, and defederating those instances means that proactive moderation ensures that most of the hate coming from bigots never needs to be moderated, because it never arrives in the first place.
Anyway, it seems from the rest of your post that you aren’t interested in engaging genuinely, so that’s that…
Not really comparable to ethnic\religious\racial hate anywhere in the civilized world.
OK, I seem to answer lots of your comments not touching the actual core of the subject.
See, “per user” moderation is good because everybody’s idea of bigotry is subjective. Bad because it’s reactive, as you said, which means it takes effort from the user.
“Per community” is sometimes acceptable, though it always gets ugly over time. I’ve been a forum mod from time to time in the late 00s, I know what I’m talking about. If you can believe me, I stop being unhinged when handed opportunity to ban people.
“Per instance” is bullshit.
See, this has already been solved for email with client-side spam filters.
Or, with social media, you can in theory have kill-lists (for users and everything they post, or for separate posts), and subscribe to those. So, just like you want, somebody bans a user and everybody subscribed to that kill-list stops seeing them. No effort required, and without compromising others’ freedom to read.
I’ve been building and developing communities, queer and otherwise for decades. I’m also trans, and live it first hand.
The per user approach puts a cost on each and every user, and that cost can sometimes be too much for vulnerable folk dealing with harassment. Blocking the bigot with a throw away account after being exposed to the bigotry is pointless, because the account was going to be abandoned anyway, and you’ve already been exposed to the raw hate.
It makes it impossible to just have fun and enjoy your social media experience when you’re always waiting for the next bigot to drop it.
Instance level blocking resolves a lot of that.
Your theory of what will work just doesn’t cut it for many vulnerable folk, and it’s not going to start cutting it just because you want to debate the topic.
I’ve described how it doesn’t.
Which doesn’t change anything as compared to instance-wide or community-wide moderation. And if you mean that you only want to see approved accounts, that can be done without instance-wide or community-wide moderation too just as well.
Nothing fundamentally prevents you from ignoring a whole instance. Or, from what I described with subscribing to kill-lists, that instance being blocked as a whole in that kill-list.
You people have gotten so used to commercial bullshit that you don’t realize how much can be done with simple things.
It obviously does, because what I’ve described works exactly the same for the user, except for them having a choice.
The issue is that users aren’t “instance based” in the same way they are on the fediverse. On the fediverse, instances are communities of like minded folk, so all of the bigots hang out in bigot friendly instances, which I simply defederate from. If they join non bigot friendly instances, they get removed
On Bluesky, bigots don’t belong to a particular instance. They just pop up with throw away accounts and have to be dealt with, one by one.
I’ve been on the fediverse longer than you my friend. I don’t use centralised social media of any type.
The issue isn’t that I “don’t realise”, it’s that what I want from a social media platform isn’t something that Bluesky offers. You want different things to me. Arguing at me as if you can make me want the same things as you is a waste of both of our times.
Bluesky doesn’t give me what I need, and it’s ultimately that simple
So a person to the kill-list of which you are subscribed does that, playing the role of a mod. There may be a few such people with their kill-lists, united by logical OR. You don’t have to do anything.
It’s just a better solution for what you claim to want.
Just say honestly that you want to ban some people in bunches and feel that it’s your bunch doing it and not you alone.
Yep. After the troll has trolled.
It’s reactive moderation, which leads to a shit experience for vulnerable people if that’s how the majority of moderation needs are met.
Because fediverse accounts are instance based, and instances have their own rules and communities, bigots tend to cluster with other bigots, and defederating those instances means that proactive moderation ensures that most of the hate coming from bigots never needs to be moderated, because it never arrives in the first place.
Anyway, it seems from the rest of your post that you aren’t interested in engaging genuinely, so that’s that…
No.
It can be proactive just as well. You’d subscribe to a whitelist instead of a blacklist. Simple.
This doesn’t have any mandatory connection to fediverse. Humans build systems.
So finally the only real argument a snowflake has.
And a ban for you