So no, gamer* would count as an uncensored instance of saying the g-word, regardless of the * in there. It uses regex to find all instances of g.mer. gmer does not count since it needs at least one character in between the g and the m. There's lots of tweaks I could make to include words like that, but haven't done any work on the bot in like a year.
Always happy to! Yeah the weirdness it can cause with the counts is fun. Breaking bots is very fun—recently the bot ran into this issue where it has to paginate so long for some users (since the site has been active for a while now, and some users have a fuck ton of comments) that it often doesn't finish the count before another process picks up the message and starts counting as well, leading to double or triple commented requests. Annoying, but haven't bothered to fix it yet.
A censored to uncensored ratio of 100% is not great. We need to learn when to be :mask-on:, if g*mer infiltration is to be successful
deleted by creator
Fuckin' lol.
I think it's g*mer.
Not sure though
deleted by creator
Ok that's good at least.
But seriously I think @thethirdgracchi is the person responsible for the bot, they know all the words it looks at and everything
@LegaliiizeIt Yeah it looks for g*mer and its equivalents as censored and stuff without any * as uncensored. You can view the source code here.
deleted by creator
So no, gamer* would count as an uncensored instance of saying the g-word, regardless of the * in there. It uses regex to find all instances of g.mer. gmer does not count since it needs at least one character in between the g and the m. There's lots of tweaks I could make to include words like that, but haven't done any work on the bot in like a year.
deleted by creator
Always happy to! Yeah the weirdness it can cause with the counts is fun. Breaking bots is very fun—recently the bot ran into this issue where it has to paginate so long for some users (since the site has been active for a while now, and some users have a fuck ton of comments) that it often doesn't finish the count before another process picks up the message and starts counting as well, leading to double or triple commented requests. Annoying, but haven't bothered to fix it yet.
deleted by creator