Dear diary,

Today, I added listeners when a message gets updated, so people can’t bypass the filter system by sending a message then editing it to a url, or something blocked. I also added another detection method that works the following way:

Message is:
“https://youtube.com meow uwu :3 also look at this 18+ video https://blocked.url”

The old system would’ve allowed this, because it’s remove any white spaces, so the message becomes:

“https://youtube.commeowuwu:3alsolookatthis18+video https://blocked.url”

Then, it’d check if it contains a blocked sequence of characters, which is “://” in that case. Then, it’d check if it contains any of the “good” domains, and if it does, it’d allow the user to send the message. That was a bad system, and I rushed it.

The new system does this:

Message gets chunked:
[“https://youtube.com”, “meow”, “uwu”, “:3”, “also”, “look”, “at”, “this”, “18+”, “video”, “https://blocked.url”]

And it iterates trough every field. So now, if a url is present in a chunk, it’d only check that url.

Also I added new translation keys.