100
submitted 1 year ago* (last edited 1 year ago) by ilovededyoupiggy@sh.itjust.works to c/main@sh.itjust.works

Edit: I've been schooled in the comments, this is no longer a thing, they've relented and allowed more control over the censor list. But hey, it's kinda funny still, so, feel free to keep reading if you like...

Original post follows.

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?

you are viewing a single comment's thread
view the rest of the comments
[-] thirdorbital@sh.itjust.works 12 points 1 year ago

I naively want to believe that this won't be an issue for most users having most conversations. But out of curiosity can you link what the ban list actually contains?

[-] wildbus8979@sh.itjust.works 9 points 1 year ago

I ran into this earlier today, I couldn't even figure out what the word was. Rewrote my message three times, and then gave up.

[-] New_account@lemmy.world 11 points 1 year ago* (last edited 1 year ago)

Gotta love when ~~classic~~ cl***ic profanity filters are implemented without learning the mistakes that have been made again and again over the last 30 years.

[-] TheTedJamesExperiment@kbin.social 8 points 1 year ago* (last edited 1 year ago)

From Software games have filters for player names and it often leads to stuff like this. Thus if you put "knight" in your character's name, a common thing that people do given that they're medieval fantasy games, it appears as "k***ht." Likewise "dead" becomes "d***" and "Thomas" becomes "T**mas." Even more embarrassingly, the filter is case sensitive and all the filtered words are lowercase, so you could name your character a slur and it would be fine as long as you capitalize the first letter.

[-] taladar@sh.itjust.works 2 points 1 year ago

It is known as the Scunthorpe problem after a town in, I think England and a certain word it contains that is often blocked.

[-] New_account@lemmy.world 2 points 1 year ago

Ahh, the word "hor." Can't let the children see such profanity.

[-] MeowdyPardner@kbin.social 7 points 1 year ago

I think you have to ask the admin of sh.itjust.works what they set the filer to because it seems customizable now.

this post was submitted on 15 Jun 2023
100 points (100.0% liked)

sh.itjust.works Main Community

7577 readers
1 users here now

Home of the sh.itjust.works instance.

Matrix

founded 1 year ago
MODERATORS