In Pokemon Go, you can assign nicknames to your Pokemon or other players that you denote as friends. Your friendship level can increase once per day if you interact with a person. While working my way up the friendship levels, I will use the nickname field to make of note of the last date I interacted with someone.
Today I marked a friend “s3/10” (s - sent a gift, 3/10 - today’s date). The software blocked it saying the name contained an “inappropriate phrase”.
“3/10” was fine. Yesterday’s “s3/9” wasn’t a problem. So what’s the deal with “s3/10”? Googling tells me nothing. Or am I happier not knowing, just like I was happy to be ignorant of the dollar amounts Jeopardy doesn’t allow to be bid. (I understood 69, 420 and 666, but was blissfully unaware of the problems with 14 and 88).
I’m curious how tomorrow works out. I can’t see any reason for this one.
My honest best guess is that their naughty words list has some data that just got entered erroneously. OR that “s3/10” might generate a naughty word in a different region if the text encoding was changed.
I played around with it some more and got a few more data points.
s3/11 - ok
s 3/10 - still bad
s 3 10 - ok
s 310 - ok
s310 - bad
Not seeing a pattern.
The exact message is “This name contains inappropriate text.”
Yeah, it doesn’t seem to pick up phonetic obscenities very well. I’ve seen “SukitBeach” and “Likkme247” (using a Clamperl, of course) in gyms around here.
Being an international game, it of course has foreign words on the naughty list. I once tried to name a Lickitung “Baise-moi”, thinking “kiss me” in French, big tongue, Frenching, hee-hee, get it? Totally forgot it can also be translated as “fuck me”. Game blocked that one.
If they are using a machine learning algorithm to identify bad names, it may just happen that that string of characters fall in some bad area of the input space for some totally unknowable reason. That is the problem with such algorithms. They are basically black boxes so when they fail it’s hard to determine why.
Good detective work. I was also thinking about the logic of the good vs. bad options, and it’s possible that the slash triggers their filter to do a second check removing all special characters, but just a space doesn’t. So “s3/10” and “s310” both get checked as “s310,” but “s 310” and “s 3 10” don’t.