You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
When logging in Blockstack requires users to enter their email address. Blockstack does not explain what the email addresses are used for, other than "recovery" (although it's not clear what exactly can be recovered using the email address, or how to go about this recovery process).
I think that if you're going to collect email addresses you could put the email addresses to good use and send users an email when the names associated with the seed they are logging in with are going to expire. One of my names apparently expired about a month ago and it's only by luck that I was able to renew it before someone else registered it.
Side note: Ideally this notification service is opt-in and users are not required to give their email address just to log-in (since email has nothing to do with the Blockstack protocol).
The text was updated successfully, but these errors were encountered:
When logging in Blockstack requires users to enter their email address. Blockstack does not explain what the email addresses are used for, other than "recovery" (although it's not clear what exactly can be recovered using the email address, or how to go about this recovery process).
I think that if you're going to collect email addresses you could put the email addresses to good use and send users an email when the names associated with the seed they are logging in with are going to expire. One of my names apparently expired about a month ago and it's only by luck that I was able to renew it before someone else registered it.
Side note: Ideally this notification service is opt-in and users are not required to give their email address just to log-in (since email has nothing to do with the Blockstack protocol).
The text was updated successfully, but these errors were encountered: