Coming here from the Great #RedditMigration. When all of the alternatives were being discussed, one thing I noticed was that Lemmy seems to have one single global slur list that’s literally hard-coded into the software. Your only option (as a server admin) is to either enable or disable it, but the words it’s going to block are permanent and unchangeable unless you can talk the devs into updating the regex for the next release.
And I checked out some of their GitHub issues, and the devs seem almost militantly defensive of this. Like, they are not entertaining any suggestions at all to make it editable. Their actual solution is, if you don’t like it, fork the repo and change it your own damn self, but we’re not touching it, go piss up a rope. Don’t mind one of the words they don’t like? Too bad. English word is perfectly innocuous in your language? Piss off. Want to block the equivalent Djiboutian words? Believe it or not, go to hell.
Seems like such a weird hill to die on. And this is concerning as the lemmyverse is just taking off. This just seems like such an easy and obvious thing to make configurable for all kinds of reasons, and they’re just closing down tickets. Not even a “don’t have time right now but we’ll put it in the backlog and get there soon”. Just, nope.
So anyways. I dunno where I’m going with this really. I’m not in a position to really do anything about it. So this is just a rant I guess. But if the main devs of this thing we’re all migrating to are this… I dunno, arrogant? Opinionated?.. already, then what’s gonna happen later when there are actual real issues that need addressed? We’re leaving one spezhole and going straight to another?
I must say it was a funny rant to read (and I 100% agree with you)
Edit: though i quickly looked at the code and it seems that the regex is customizable? https://github.com/LemmyNet/lemmy/blob/main/crates/api_crud/src/site/update.rs#L126
I’m glad they’ve relented and made it editable now! The threads I’d seen mastodon about it, and the links to their GitHub tickets, were pretty disappointing to me. Glad it’s not the case anymore.
FWIW it’s been this way for well over a year IIRC.
But the instance you post on needs to have it configured reasonably too.