Re:Username ending with MIME type format is not allowed
by walty8 on Wednesday September 15, 2021 @02:25AM
(#28535876)
But the in the screen capture of article, the user name is actually 'issac.asimov', i.e. the mime type does not immediately follow the dot.
[ Parent
| on HN ]
Re:Username ending with MIME type format is not allowed
by nobody9999 on Wednesday September 15, 2021 @03:14AM
(#28536189)
>But the in the screen capture of article, the user name is actually 'issac.asimov', i.e. the mime type does not immediately follow the dot.
A variation on the Scunthorpe Problem[0] then, eh?
Re:Username ending with MIME type format is not allowed
by whizzter on Wednesday September 15, 2021 @03:32AM
(#28536295)
Somebody probably put in a regexp with .mov$ , however for regexps the dot (.) matches everything (and $ matches end) so the i in asimov is eaten regardless and then the rest of the match succeeds.
Re:Username ending with MIME type format is not allowed
by chippiewill on Wednesday September 15, 2021 @04:34AM
(#28536683)
You can see the fix they made in the linked MR.
It wasn't a regex, they just did a generic "ends with" check.
Re:Username ending with MIME type format is not allowed
by iechoz6H on Wednesday September 15, 2021 @03:35AM
(#28536325)
Perhaps the sub-clause is redundant there?
'The problem was named after an incident in 1996 in which AOL's profanity filter prevented residents of the town of Scunthorpe, Lincolnshire, England, from creating accounts with AOL, because the town's name contains the substring "cunt".'
Re:Username ending with MIME type format is not allowed
by nobody9999 on Wednesday September 15, 2021 @07:06AM
(#28537597)
>'The problem was named after an incident in 1996 in which AOL's profanity filter prevented residents of the town of Scunthorpe, Lincolnshire, England, from creating accounts with AOL, because the town's name contains the substring "cunt".'
Right. Regardless of the specific pattern matching function, in both cases, the results were both incorrect and unwanted. Which is why I consider this instance to be a variation on the same issue.