By becoming paternalistic, the engine starts becoming what it criticizes. It’s better if users themselves can choose what they want / don’t want to see.
If a user wants to see that, they are free to make an account on the triad themselves, admins should not have to platform their toxicity and misinformation.
And it’s also toxic to user uptake in general, a Threadiverse veteran will know what to block, a brand new user on the cusp of breaking from Big Tech social media won’t. They’ll see that crap and bail, then go on to talk about how they “tried that threadiverse stuff and found a whole bunch of pro-Russia/DPRK simps”
Still, baked into the engine, it doesn’t have a healthy prospect. If someone ill intended is involved, he/she can use such an instance as a distraction to set a precedent and narrow further and further what people can and can’t see. And when those that would previously applause it notice the problem, it has the risk of being too late.
At the end of the day though. It isn’t the instances themselves which are actually the problem. Rather the people on them. We can rightfully rail against them all day long as much as we want. And they do give us plenty daily to point out all their flaws.
It also won’t change the fact that many of them can and already have set up shop on other servers as well. Even if you blocked every domain ending in ML. That type isn’t going away. If anything those instances do quite a bit to contain/expose them.
The problem with defaulting a software to cut them off. Is akin to those trying to legislate morality. When morality is legislated, no one is moral. Because there is no choice or consent. Likewise a “boycott” entered into without knowledge and consent, isn’t really a “boycott”. Can we beat them by becoming like them? I’m not so sure.
https://feddit.online/, the same way https://fedia.io/ does (by the way, Fedia isn’t a software, it’s called Mbin, and doesn’t have such code, so not sure why you’re including them into your title)
https://quokk.au/, it used to be the same when it was still a Lemmy instance
Social media tends toward extremes and it takes man hours to do moderation. Instead of continuously banning hexbear users it would be better to just ban the instance.
By becoming paternalistic, the engine starts becoming what it criticizes. It’s better if users themselves can choose what they want / don’t want to see.
If a user wants to see that, they are free to make an account on the triad themselves, admins should not have to platform their toxicity and misinformation.
And it’s also toxic to user uptake in general, a Threadiverse veteran will know what to block, a brand new user on the cusp of breaking from Big Tech social media won’t. They’ll see that crap and bail, then go on to talk about how they “tried that threadiverse stuff and found a whole bunch of pro-Russia/DPRK simps”
Still, baked into the engine, it doesn’t have a healthy prospect. If someone ill intended is involved, he/she can use such an instance as a distraction to set a precedent and narrow further and further what people can and can’t see. And when those that would previously applause it notice the problem, it has the risk of being too late.
At the end of the day though. It isn’t the instances themselves which are actually the problem. Rather the people on them. We can rightfully rail against them all day long as much as we want. And they do give us plenty daily to point out all their flaws.
It also won’t change the fact that many of them can and already have set up shop on other servers as well. Even if you blocked every domain ending in ML. That type isn’t going away. If anything those instances do quite a bit to contain/expose them.
The problem with defaulting a software to cut them off. Is akin to those trying to legislate morality. When morality is legislated, no one is moral. Because there is no choice or consent. Likewise a “boycott” entered into without knowledge and consent, isn’t really a “boycott”. Can we beat them by becoming like them? I’m not so sure.
Example of two Piefed instances that currently federate hexbear:
List of Piefed instances that currently defederate hexbear:
https://piefed.fediverse.observer/list
As you can see, instances defederating hexbear are instances managed by teams which were going to do so anyway, as they already did on Lemmy.
Instances who want to federate know how to do so, there are three examples.
I think that is only partially true
Social media tends toward extremes and it takes man hours to do moderation. Instead of continuously banning hexbear users it would be better to just ban the instance.