Look at here and the people who complain about it being too hard to figure out are the ones complaining about “I can’t use muh slurs, this is awful.”
“The left of today is very much in favour of censorship to avoid “harm.” This makes those of us in the middle very wary of signing up to any partisan media.” /u/decidedlysticky23
/u/misshapensteed claims he isn’t far right, but explictly only posts on PoliticalCompassMemes and TheLeftCantMeme and KotakuInAction.
If they are too stupid to figure out we know they’re lying, they’re too stupid to figure out lemmy.
You must log in or register to comment.
I don’t see an issue with slur filter either but from what I’ve read it was hardcoded and couldn’t be customized by other instances. Can you explain the reasoning behind that, why not let instances decide how far they want to go with their censoring policies? In my experience the only good moderation is manual context-aware moderation done by a person, text filters accomplish nothing except making people come up with slang terms or other workarounds. Seems weird to have this policy enforced in this way.
It’s open source software. You could even then remove the slur filter manually trivially, and with a small amount of technical skill, make that persist across updates.
It took them quite some time to move it to a user friendly place. It can be set in the server settings in the UI presented to administrators. Previously it was hard coded requiring a fork or maintaining code every update.
However, I’d like to highlight that many people interested in federated software are not as technically proficient as you are. Your thoughts on what is challenging probably doesn’t match what less technically proficient users think of as challenging. If federated software is to succeed, it needs to be approachable to many different kinds of people, not just the most tech literate of us.
