Every post about lemmy invariably descends into criticism of us 2 devs leftist politics. Its a spectre that won’t go away even tho we plan on externalizing the existing slurs ( an externalized slur filter has already been in lemmy for months ).
Yeah, it is odd how much weight is put into the slur filter and how quickly the discussion gets to the slur filter when the code is open source. I wish the discussion was focused past that and on more constructive issues but \ ’ ’ / . I imagine it is more of a vocal minority commenting in the thread on these topics. It will be interesting to see if there is an influx of users.
Do not remove the hard-coded slur filter! I am a serious person, I do not use slurs I do not use the F word, when I get angry at someone I give constructive criticism or just don’t reply. Trolls are not serious people, so each time you accommodate a troll, you alienate another serious individual. Do not capitulate to trolls! nobody who has anything serious to say will need slurs to do it.
Oh ok. I was worried for a second that the entirely of the filter was being moved to an external configuration.
Also I literally just now ran into this issue. If I try to go to https://lemmy.ml/inbox I get a 502 gateway error. But it works fine if I first go to https://lemmy.ml and click on the notification bell. Do you know anything about this? Let me know if you want me to create an issue for this.
Oh ok. I was worried for a second that the entirely of the filter was being moved to an external configuration.
I really don’t like it either, but I think this is the way we’re going, for the next major release. We’ll of course apply that existing list to this instance, and possibly have that list in the default config.
I really don’t want to remove it, because every time I’m tempted to, I realize that its one less bigoted group that’s going to use lemmy. But now that lemmy has grown a bit, it seems that they’re avoiding us anyway. Most importantly we have a core cluster of instances now that are all devoted to enforcing the no-bigotry policy. That’s enough momentum (i think), to be able to remove it without worrying too much.
I’ve honestly never been bothered by the filter and don’t see the point of removing it when the only people wringing their hands over it are toxic. There’s another site running lemmy that added mandatory pronouns (+neopronouns) and some people threw such a giant fit over it that you immediately knew who to avoid. It’s like a canary for user morality.
I think not removing it fine but that is just my opinion. One thing that can be done is remove words that cause issues in non-English languages.
My opinion about the filter is a bit idealistic because it does keep a certain kind of people of the platform but it would hinder adoption. You should just ponder over it every three or six months with the other dev.
Ahh the other issue I’m not sure about, ya make an issue on lemmy-ui, I’ll probably have to pull down the DB to test this locally, because I’m not getting it for my user.
deleted by creator
Every post about lemmy invariably descends into criticism of us 2 devs leftist politics. Its a spectre that won’t go away even tho we plan on externalizing the existing slurs ( an externalized slur filter has already been in lemmy for months ).
Yeah, it is odd how much weight is put into the slur filter and how quickly the discussion gets to the slur filter when the code is open source. I wish the discussion was focused past that and on more constructive issues but \ ’ ’ / . I imagine it is more of a vocal minority commenting in the thread on these topics. It will be interesting to see if there is an influx of users.
Do not remove the hard-coded slur filter! I am a serious person, I do not use slurs I do not use the F word, when I get angry at someone I give constructive criticism or just don’t reply. Trolls are not serious people, so each time you accommodate a troll, you alienate another serious individual. Do not capitulate to trolls! nobody who has anything serious to say will need slurs to do it.
What does this mean?
A few months ago we added a config that allows you to add additional slurs to be filtered, that aren’t in the existing hard-coded list: https://github.com/lemmynet/lemmy/blob/main/config/config.hjson#L93
Oh ok. I was worried for a second that the entirely of the filter was being moved to an external configuration.
Also I literally just now ran into this issue. If I try to go to https://lemmy.ml/inbox I get a 502 gateway error. But it works fine if I first go to https://lemmy.ml and click on the notification bell. Do you know anything about this? Let me know if you want me to create an issue for this.
I really don’t like it either, but I think this is the way we’re going, for the next major release. We’ll of course apply that existing list to this instance, and possibly have that list in the default config.
I really don’t want to remove it, because every time I’m tempted to, I realize that its one less bigoted group that’s going to use lemmy. But now that lemmy has grown a bit, it seems that they’re avoiding us anyway. Most importantly we have a core cluster of instances now that are all devoted to enforcing the no-bigotry policy. That’s enough momentum (i think), to be able to remove it without worrying too much.
I’ve honestly never been bothered by the filter and don’t see the point of removing it when the only people wringing their hands over it are toxic. There’s another site running lemmy that added mandatory pronouns (+neopronouns) and some people threw such a giant fit over it that you immediately knew who to avoid. It’s like a canary for user morality.
I think not removing it fine but that is just my opinion. One thing that can be done is remove words that cause issues in non-English languages.
My opinion about the filter is a bit idealistic because it does keep a certain kind of people of the platform but it would hinder adoption. You should just ponder over it every three or six months with the other dev.
Ahh the other issue I’m not sure about, ya make an issue on lemmy-ui, I’ll probably have to pull down the DB to test this locally, because I’m not getting it for my user.