Indeed. And it’s a needlessly destructive form of sanitization. That is, sanitizing properly normally means replacing the special characters with an encoding to ensure literals render.
I think this is a regression. IIRC, there was a time when a removal only removed it from the timeline. You could still reach it via the modlog. IIRC. But those days are gone. It’s a shame because it’s important for the community to be able to evaluate the mod’s decision making.
I’ve even seen cases where an over-zealous mod gets embarrassed by the mod log and purges the mod log itself to remove traces of the censorship itself. I suppose that’s only possible if the mod is also an admin.
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]).
I can see your point in many situations but when I say I am the one b*tching (myself… in the 1st person), in this context I am not saying I am acting badly myself. So the “women are bad” narrative doesn’t follow. In this case the word merely serves as a more expressive complaint.
If someone were to talk about someone else b*tching, it might well be what you’re saying, as they are complaining about someone else complaining & maybe they oppose that other person complaining or their aggressive style thereof.
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]).
So does that mean jlai.lu is blocked by lecho.be? I figured it was more likely that lecho.be was blocking Tor, thus blocking my connection.