I think you're better off changing instances to one that doesn't use the filter.
Do you know what I should look for? Is it the version number? I recall Lemmy was forked to Lenny, but not sure how to recognize Lenny instances.
(btw, fwiw, I wouldn’t use sh.itjust.works because that’s even more nannied [by Cloudflare]).
It's not a fork or version number thing. It's just a instance admin toggle as far as I'm aware.
Lemmy.ml was actually the only one I knew of previously with it enabled.
sh.itjust.works, lemmy.ca, lemmy.world, etc all dont have the filter.
Have you messaged your instance admin? They may not be fully aware of the implications of having the filter on.
And regarding cloudflair at least on sh.itjust.works we're still hoping its a temporary measure.
I don't think lemmy comes with a filter enabled by default, so you could probably move to most other instances
Correct it does not, it looks like this by default.
I was thinking the "b" word was bank and was confused af
Purged by creator
I agree with those that say if you cannot live with the filter you should pick a new instance. Part of this whole experiment is that each admin is going to go with defaults they are comfortable with, and as a user you need to be respectful of those, or move on.
I do you agree with you that REDACTED works better in this case than "removed", as I always see "removed" as a user action for whatever reason. Even the use of something like FILTERED would immediately alert the user and others that the original word(s) was/were removed and a basic understanding of why (it triggered the slur filter somehow).
I guess I would also go and change the "slur" filter language to just language filter, as not everyone is going to agree on everything an admin may want to filter being a "slur", it could be any taboo word in that admins location.
There are bug reports and then there is user support. There’s some confusion because I filed a bug report in a user support community (because there is no bug reporting community).
Indeed the user support solution is to either request that the admin to change the slur filter config, or change instances. But the purpose of the thread was to report a bug in an in-band way (without interacting with a Microsoft asset [#deleteGithub]).
It's not really a bug though, as it is working as intended. You may not like that implementation, so you would want to see an enhancement to the code.
Lemmy Support
Support / questions about Lemmy.