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.
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.