3 ms·
> Whoever decided that email verification was a poor user experience needs to be hit in the head with a shovel after he digs the appropriate sized hole. That's
by zeveb 10y ago
> Whoever decided that email verification was a poor user experience needs to be hit in the head with a shovel after he digs the appropriate sized hole.
That's why you get send the verification email first, when creating the application user, and don't do anything until the email is verified.
The flow should be:
User: Please give me an account; my email address is jim@example.invalid
Server: I have sent an email to jim@example.invalid
Server → jim@example.invalid: Please go to https://server.invalid/register?token=KDU6dG9rZW4xOWppbUBleGFtcGxlLmludmFsaWQxMzoyMDE3MDMxN1QxNDEzNjQ6yzd8ELD1piyANiWnmdnpCL5F52f10UfUdEkHywVZeqTt0ymgrxR63Qz0GB7TKPoeeZQmWCaz7T1-9vBnypkYWik https://server.invalid/register?token=KDU6dG9rZW4xOWppbUBleG...
User: visits URL, completes registration
- camiller 10y agoThat is what I was trying to say. Apparently there is some number of designers that believe that that whole email verification process is too much friction for registering a user, so they simply opt not to do it at all.