Viewing a single comment thread. View all comments

celebratedrecluse wrote

Btw Does this include usernames?

1

ziq OP wrote

No

2

celebratedrecluse wrote

Ah, that explains. there was a user, you probably saw already, who had the slur in names. So this could be a future problem for spam; the body of the text will just contain fashy content which is designed to evade the filter, but the name itself will be extremely vulgar.

Still this is a great development! automating this labor will ease the burden on administrators, ihope

2

ziq OP wrote (edited )

Yeah seeing that user in the ban log is why I thought it wouldn't be covered but according to emma it's covered if it's the full phrase or if 'regex' mode is used instead of 'text' mode.

Like if 'badger' is the 'text' phrase we block but the username is 'evilbadger', it will make it through the filter.

But there's also a 'regex' function I haven't tried yet, and I guess that will block 'evilbadger' if I understand emma right.

So I was wrong and usernames are covered, I just need to change slurs to 'regex' instead of 'text'.

EDIT: Yeah I just made a new regex rule for the n word and tried to make a new account with the n word in it and was blocked from doing so. So usernames with slurs will now be blocked too.

2

emma wrote (edited )

Regexes are case-sensitive, though, so you need to prefix each of them with (?i). Also b*tchmedia links aren't going to work.

The best way to block slurs in usernames would be the regex (?i)^\w*slur\w*$, I think. This matches only the presence of the slur in a line comprised of a single word, e.g. usernames, letting URLs containing the word pass.

2

emma wrote (edited )

Yes (but the 'text' type only matches whole words)

2