Re:Email Verification Protocol
by tytho on Sunday November 09, 2025 @09:52AM
(#45865966)
Many applications need a way to contact a user (security breach, password reset). If one only has a username and forgets the password, there’s no way to reverify the user.
[ Parent
| on HN ]
You don't need to validate email for that.
Re:Email Verification Protocol
by thedelanyo on Sunday November 09, 2025 @01:09PM
(#45867637)
I think if you're not verifying emails, you'll also receive lots of bot signups.
There are many ways to re-verify the user if one forgets a password. Some may even be more secure than sending a e-mail. Simplest is a set of single-use reset codes that could be generated at signup or later on, like the ones to remove 2FA.
> If one only has a username and forgets the password, there’s no way to reverify the user.
Tough beans?
Re:Email Verification Protocol
by crazygringo on Sunday November 09, 2025 @10:38AM
(#45866294)
A good user experience does its best to avoid tough beans. That's kind of UX 101.
In the case of security procedures, I'd argue that there is some room for tough beans. Reducing security to cater for carelessness seems like a really bad compromise to me, one that I see far too often.
Re:Email Verification Protocol
by crazygringo on Sunday November 09, 2025 @11:48AM
(#45866894)
But it had to be a balance. Ultimate security is for a good experience too -- not having your account stolen.
If you go too far so tons of people get permanently locked out of their accounts, so a handful of people's accounts don't get compromised when their email has been compromised, that doesn't seem like the right tradeoff. Especially if it's not something like e.g. banking.
Re:Email Verification Protocol
by tsimionescu on Monday November 10, 2025 @02:13AM
(#45873277)
This is an absurd position, and potentially illegal - for paid services.
You have a business relationship between the company and a person. Whether that person remembers the password or not is immaterial to whether they have the legal right to anything they purchased in the app.
Having your account taken over is also a bad user experience.
> Many applications need a way to contact a user … password reset
At this point the password is pointless, you might as well just use the email address. Or perhaps a distinct username and email address, but then there would probably be a “forgot username” workflow making that as pointless as the separate password.