this post was submitted on 06 Jun 2023
212 points (100.0% liked)
Chat
7499 readers
21 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.