<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dick Hardt wrote:
<blockquote cite="midEE614930-CF89-4F3C-8A2D-B1688B02C2EA@gmail.com"
type="cite">...
<blockquote type="cite">
<pre wrap="">For instance, many websites require a verified email address to
register.
</pre>
</blockquote>
<pre wrap=""><!---->
It would be useful to understand why the website wants a verified
email address, as it may not be required when an identity protocol is
available.
A number of reasons come to mind:
1) password reset mechanism
2) further assurance there is a person on the other end instead of a bot
3) push info to the user via SMTP
There are other ways to do (2) and (1) is really an identity protocol.
(3) is shifting with the rise of SMS and other messaging as email
declines from the use of spam.
</pre>
</blockquote>
#2 is not very useful at this point unless combined with email provider
blacklists<br>
#3 is useful but there are many, many application that don't need an
email address unless the user actually gives consent. If this happens
as part of login/signup and is absolutely required, then yes, it's
useful at that point. I think this is a minority use case (or should
be).<br>
<br>
I can also think of #4: I have existing legacy systems that are based
on having the verified email address (especially as a foreign key), and
want to migrate incrementally, if at all.<br>
</body>
</html>