News for hackers. Stuff that matters.

A comment on Red Hat OpenShift.io – Free, end-to-end, cloud-native development. Parent comment

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by noja on Tuesday May 02, 2017 @01:53PM (#14248756)
Then it's a bug right? The uniqueness check should be based on the part before the + sign.
[ Parent | on HN ]
Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by thanksgiving on Tuesday May 02, 2017 @08:06PM (#14251926)
No, I don't think what google does is standard behavior (not trying to say anything bad about Google; I love Google). However, as far as I know, disallowing + is not a particularly good way of preventing abuse. I won't go as far as to say it semms like bad code but it is pretty close.

I think it is OK to make a special case for Gmail and Google mail but it is counterproductive to try to crown it as a de facto standard.

http://mozilla.wikia.com/wiki/User:Me_at_work/plushaters?use...

[ Parent | on HN ]
Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by noja on Wednesday May 03, 2017 @03:59AM (#14253832)
huh? Google's special behaviour is that they are blind to dots in the user part of the address.

The + sign is not anything to do with Google.

[ Parent | on HN ]
Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by thanksgiving on Thursday May 04, 2017 @03:33AM (#14263195)
Oh I didn't know. Just found https://tools.ietf.org/html/rfc5233 after trading what you wrote.

I just assumed + is a valid character and [email protected] would be a valid email address independent of a or b. But it seems we shouldn't allow + or -- when people sign up for a new email address?

[ Parent | on HN ]