> There's no inherent reason to have an identity separate from the one the site you're joining grants you. What do you mean? > I'd guess that site is leveragi

> There's no inherent reason to have an identity separate from the one the site you're joining grants you. What do you mean? > I'd guess that site is leveraging the effort which webmail providers spend to weed out bots and sock-puppets. And perhaps they use the address for adtech purposes. But I don't know for sure. It’s a lot like having a physical address which is used as a core part of meatspace identity management. > I'd love to hear from such sites about how they use customer email. If it's not primarily for communication, it may not make sense to accommodate it in TMTP. A shared unique identifier (value for user is that it is consistent across services). A means of authentication when primary auth (password) cant be used (company sends links etc). 1-1 channel of communication (notifications of activity or changes in a service). Obviously, it’s just my opinion, but making a new messaging protocol won’t fix email. My hunch is that is because email’s primary purpose (to the end user) is not to provide a messaging channel but to provide an identity.