4 ms·
It's not the fact that software engineering is broken saddens me as much as the extent. Email is older than absolute majority of active developers and yet, it
by friendzis 2y ago
It's not the fact that software engineering is broken saddens me as much as the extent.
Email is older than absolute majority of active developers and yet, it seems, simple knowledge like "what is email address" remains such an arcane knowledge that you are being looked at weird when present something a tiny little bit more correct than the status quo.
Where else can we assume that the common knowledge is flat out wrong?
- Akronymus 2y ago>"what is email address" Anything you can send an email to that is received, as far as I am concerned. I have my own domain, so why ahould I be forced to add an arbitrarily long string to it to be able to receive the mail? Or exclude <site>@myDomain.com from being input on <site>? Or the worst of the worst: Disallow all but a few domains for emails. At this point, not validating it cient side at all is IMO the correct approach, and instead send a verification email.
- friendzis 2y ago> Anything you can send an email to that is received, as far as I am concerned. 100% this. The only acceptable hard validation is to check whether there is an @ between some characters. something like `.@.` in regex. It makes sense to do sanity checking (soft validation) on client side. There is 99.9% chance that `muppet@gmial.com` is wrong, outright rejecting that is wrong, though.