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.
GDPR gives people a fair amount of protection and it is enforced.
Not in my experience. I have filed complaints of ~20+ GDPR violations under article 77 going years back. Not a single one of them enforced to date. These cases just sit idle for years. The problem is the GDPR gives no recourse when DPAs fail to honor article 77 obligations. It’s toothless.
That shows a low count of cherry-picked enforcement actions. If you had a way to get a count of unenforced reports it would likely be an embarrassing comparison.
You should simply pickup a few dictionaries and recognize there are multiple meanings, rather than cherry picking whatever definition plays into whatever narrative you’re fixated on. Have a look at mainstream definitions that most people are commonly working with.
One dictionary defines it as “the feeling of hating that a man has for women”. Another dictionary: “hatred of women”. Another: “Hatred of, contempt for, or prejudice against women”. Did alternate definitions not survive your whatever cleansing you’ve undergone? Is there a specific book that caused you to deviate from common definitions?
I would avoid trying to pin down absolutes. If you’re looking for absolutes you won’t get that from me.
However generally when a woman uses the word it’s not a reflection of a derogatory attitude toward women but rather just one or a few they are referring to in particular. Of course self hate & hating one’s own people w/same attributes is certainly possible, which is why you’re not getting any absolutes here.
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]).
Indeed people with malicious intentions will get around the filter anyway. It’s the non-malicious authors who get burnt by this filter.
but it is still considered misogynistic
Men and women both use that word and when a woman uses it, it’s not misogyny because it’s directed at a specific woman (not a demonstration of hatred of women generally). It usage has murky origins but it can’t be assumed that the author is even conscious of that. The bot is making a blunt blanket decision that it can’t, and it assumes the worst of people.
The other two bugs I mention are bugs regardless of how justified or true the positive detection is.
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.