This seems to be becoming the hot topic, the elephant in the chatroom - the balance between censorship / freedom of speech on lemmy. There are solid arguments for both ways, and good compromises too.
IMO the FAQ makes it quite clear what the devs have built here, and why. But recent discussions, arguments, make it clear that a lot of the most vocal users object to it.
I’m very curious. Many active users feel this way? Please vote using the up arrows in the comments.
I wouldn’t consider a hardcoded slur blacklist censorship. I would prefer if it wasn’t hardcoded and rather a text file sysadmins would create, but it’s not censorship.
Anyone who complains about not being able to use slurs is basically outing themselves as assholes as far as I’m concerned.
Exactly. Swear words like shit and fuck aren’t “censored”. The only words in the slur filter are actual slurs, words pretty much specifically meant to insult people, often an already marginalized group. The filter is not perfect and can be problematic with non-English instances, but in those cases, admins can just edit the source code to eliminate the false positives.
The problem is that people are inserting their own political opinions into software, and it simply put doesn’t belong their.
Regarding code of conducts too, my opinion is simply “we do not care about your political opinion, please don’t share it with us”. Software should not be a political tool
depends on the slur. For example, some people like to be called whøre, myself included.
Agreed on the list and also it should be be easily admin controllable. There was an issue a while back where it was impacting a foreign language instance and one of the suggestions in lemmy support was to recompile the backend.
I think of lemmy itself as primarily a software project and have a lot of admiration for the devs.
The community on the flagship can sometimes be an echo chamber when it comes to censorship but cest la vie.
Except it is. Just not from the frontend. It’s actually extremely easy to search for the slur filter in the source code and edit it (we instructed a Danish instance to do this because some benign words in Danish look like slurs in English). It actually doesn’t take much effort to edit the filter and recompile for a specific instance, and I think if you’re going to be administering a public facing server, you should be able to do that.
However, most of the freeze peach crowd that actively want to drop slurs (note, not just swear words like shit and fuck, those aren’t “censored”, but slurs, words pretty much specifically meant to insult people, often an already marginalized group) are turned off by the very existence of the slur filter, which I imagine stops a lot of them from coming over. To me, that means the slur filter is mostly effective.
I respect your opinion and disagree. This sort of stereotype “freeze peach crowd” (which I don’t understand but I think it is derogatory) bugs me, but that’s your perogative. I admire your activity in the community.
Hmm…well if it’s so easily configurable that’s not too bad. It would be nice if you could configure it in the FE tho, but making it easily editable is a HUGE step in the right direction. Good to know that this is the case, ty
Ran into it being pretty silly with applying to removedute and other silly cases.
But that’s imperfect implementation, not a censorship issue lol.