5 ms·
This wouldn’t even let in .info…
by pwdisswordfishc 3y ago
This wouldn’t even let in .info…
- marcosdumay 3y agoYes... You didn't make a point, so I'm guessing it's just an observation. Or, seriously, not supporting .info won't stop a lot of people from adopting and keeping a system, not a lot of developers from doing things this way.
- jjeaff 3y agoYou'd be surprised. Especially if you are building B2B and users want to use their company emails. Blocking any non-standard TLDs will create a customer service pain for any reasonably large business.
- chrismorgan 3y agoI’ve been exclusively using email address(es) at my .info domain for over twelve years now. To my recollection, I’ve had issues due to the domain name exactly once, about two years ago; in that case it was a website with a bad email validation regex, and, being a web developer, I was able to bypass it, and the backend accepted it. Now I do recall noticing things that would baulk at five-character TLDs once or twice more. (Actually-deployed stuff, this is—if I counted example email address validation regular expressions I’ve seen from Stack Overflow and similar and “see how good/bad/otherwise this LLM is”, it’d be quite a few more.)