Hacker News Reader

Comment by kitd | Hacker News Reader

This is really cool!

2 points:

1. it fiddled with my back button which is a bit annoying

2. a better email sample is

    ^[^@]+@[^@]+\.[^@]+$

which removes the 2 ampersands problem.

View on HN

Even that is wrong because you can have privately owned TLDs (I forget what they're technically called) like .google

So sundar.pichai@google is technically a valid address (whether .google has any MX records is another matter)

Regex shouldn't really be used for email addresses anyway because the only reliable way to authenticate an email address is to literally send an email to that address.

.google does not have any MX records

No, but theoretically it could.

AFAIK none of the TLDs allow for MX records on just the TLD

i.e. johndoe@com will never exist

What about things like root@localhost?

I'm not on about gTLDs like .com, I'm on about the privately owned ones like .amazon and .google

I didn't say gTLDs. The id est applies to all.

TLDs can be managed very differently depending on the owners so I don't think it's safe to assume "applies to all" just because there is a rule in place for some gTLDs.

You'll probably want to add \S to those character classes as well, or it matches "it's an @ sign. not an ampersand."

Escaped or quoted whitespace is allowed in the local part of email addresses.

Thank you!

I think I know what's wrong with your back button. I will fix it.

And for the regex. will try it out and see if I can add it.

That's not how the spec works. Compliant solution: https://stackoverflow.com/a/1917982

Reply on news.ycombinator.com