Recently there have been some discussions about the political stances of the Lemmy developers and site admins. To clear up some misconceptions: Lemmy is run by a team of people with different ideologies, including anti-capitalist, communist, anarchist, and others. While @dessalines and I are communists, we take decisions collectively, and don’t demand that anyone adopt our views or convert to our ideologies. We wouldn’t devote so much time to building a federated site otherwise.
What’s important to us is that you follow the site rules and Code of Conduct. Meaning primarily, no-bigotry, and being respectful towards others. As long as that is the case, we can get along perfectly fine.
In general we are open for constructive feedback, so please contact any member of the admin team if you have an idea how to improve Lemmy.
Slur Filter
We also noticed a consistent criticism of the built-in slur filter in Lemmy. Not so much on lemmy.ml itself, but whenever Lemmy is recommended elsewhere, a few usual suspects keep bringing it up. To these people we say the following: we are using the slur filter as a tool to keep a friendly atmosphere, and prevent racists, sexists and other bigots from using Lemmy. Its existence alone has lead many of them to not make an account, or run an instance: a clear net positive.
You can see for yourself the words which are blocked (content warning, link here). Note that it doesn’t include any simple swear words, but only slurs which are used to insult and attack other people. If you want to use any of these words, then please stay on one of the many platforms that permit them. Lemmy is not for you, and we don’t want you here.
We are fully aware that the slur filter is not perfect. It is made for American English, and can give false positives in other languages or dialects. We are totally willing to fix such problems on a case by case basis, simply open an issue in our repo with a description of the problem.
Isn’t instance-blocking alone sufficient for being able to prevent the environment from being overrun? I understand the hesitancy to platform reactionaries, but as it stands the network effect is easily the biggest hurdle the Fediverse is going to face. Right-libertarians and actual reactionaries might be a net negative on the main instance, but as far as the software itself goes, numbers are numbers, and could end up making a world of difference.
Let them form their own circlejerks away from everyone else and have slur-blocking be on a per-instance basis, after all that’s why the federated design works so well.
There are more important things than making numbers go up. Just the existance of the slur filter makes right-wingers upset, and stops them from even considering to use Lemmy. That makes our job much easier because we dont have to deal with them.
I disagree just due to the aforementioned network effect. Numbers with social media have a snowball effect, where people make their decision on whether or not to participate based on existing levels of activity. What sets Lemmy apart from stuff like Lobste.rs and HackerNews IMO is that it’s integration of federation gives it potential to break out as a serious alternative to the platforms rather than catering a specific niche, so I’d say the snowballing is important also since it has the potential to help bring up the rest of the Fediverse.
Given Lemmy’s reputation as being a platform run by communists, the fact that such a hardcoded filter even existed to begin with, and also per-instance blocking/slur filtering, I’d think that should be enough to keep them away and stop them from polluting the communities associated with the flagship instances, then again I’m not an admin so I can’t say for sure. It’d also help the issue you mentioned regarding ambiguity of what slurs to include, since each community can decide that for themselves.
Lemmy is growing quite well, one year ago we only had 800 users, now we are already at 13.000. Sure the slur filter might limit growth a bit, but we are not a silicon valley company whose goal is growth at any cost.
Gfdy
Can’t they just remove the slur filter, recompile and join the federated network with their instance?
Would take a lot of effort and would be immediately unfederated when it was noticed. Not worth the time investment