bug: Hard word mutes don't filter out posts

Created by: Jegler

💡 Summary

Posts containing words from the hard mute word list aren't always filtered out from timelines

🥰 Expected Behavior

The posts aren't visible in timelines

🤬 Actual Behavior

The posts are visible in timelines

📝 Steps to Reproduce

1. add a word to the hard mute filter list
2. make a post containing the word from another account

💻 Frontend Environment

* Model and OS of the device(s): Desktop (5900x, 32gb ram, 6700xt) EndeavourOS 2023.08.05
* Browser: Firefox 121.0
* Server URL: plasmatrap.com
* Misskey: 2024.1.0.beta1

🛰️ Backend Environment (for server admin)

No response

Do you want to address this bug yourself?

• Yes, I will patch the bug myself and send a pull request

mentioned in commit a896c39d

looks like this is happening again, per several reports it seems to happen with a new update

wait why was this closed? damn you gitlab, that commit was referencing a github issue, not this one

reopened

changed the description

can you provide some concrete examples? the your list of hard muted words, and a post that shows up but should be hidden, would be perfect @nune

(top image partially censored due to sensitive nature) i mute all nsfw-related content using the hard word mutes, and these showed up

ah yes it's technically "working as intended"

lewd is not the same as Lewd ☹️

if you want to cover both, you have to list them both (in different lines)

or, you could write /\blewd\b/i to cover all capitalisations

yes, it's not great, we'll find a way to make it more human-friendly at some point

for that "regular expression":

• the two / indicate it's a regular expression and not a simple word
• the \b mean "word boundary"; if you wanted to mute all words starting with "lewd" you would write /\blewd/i, if you wanted to mute all words contaning "lewd" you would write /lewd/i
• the i at the end means "case insensitive", i.e. ignore capitalisation

the thing is that it removed all posts marked that before, even if capitalized

I… don't think that was ever the case. The code to check muted words hasn't changed in years, and people have been complaining about case-sensitivty for about as long as I can remember…

(I ask mainly because I have just tested things and everything looks fine… so without more details, I can't do much)

added bugfrontend label