Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Automatically restore all IDs on restore #1550
Relevant forum discussion: https://forum.blockstack.org/t/proposal-auto-fetch-ids-with-activity/5658
I think this task me be too large to fit into this sprint, and I don't think the forum solution addresses the main issue that most users will run into, which is that their ID doesn't resolve while it's still processing.
changed the title
Automatically restore IDs on restore – post solution in forum and decide on path fwd.
Aug 3, 2018
Why does it have to be a complicated "activity" to solve this issue, when a short term solution could be made by just storing the number of ids to generate in the
If it's a privacy issue (with putting the number in the profile.json) then just encrypt it with the bip39 mnemonic & AES or the
Introducing more state in the system doesn’t help anyone that already has multiple ids & is a bigger change than automatically searching.
We’re blocked by these other issues because we want the functionality in a library so that other developers can use it and not in the browser where it doesn’t belong.
“Temporary” solutions have a tendency to become permanent and expensive to change as other people start to rely on the temporary solution.
The current UX for multiple IDs is still poor. I read through the linked issues and forum posts, and I'm not really understanding the problem with just restoring all names/identities on account restoration.
Perhaps with a limit of around 10-20 due to how slow our crypto appears to be when restoring (haven't debugged / profiled completely yet, idk if this would actually be a problem or not).
If a user creates an ID they no longer want, let's say at the second index (identity number 2), and has a few identities that they do want after the second index, then they still have to deal with that unwanted ID with the current UX when doing the manual "add new ID" weird UX that restores one at a time. So we wouldn't really be making this issue worse.
Also, it seems easy to add an
I don’t see any problem with automatically restoring - it just never got done.
Another approach to unwanted IDs could be to hide IDs that don’t have names associated with them.
If the user wants to delete the ID they’d have to revoke the name. (Send a revoke transaction)
IDs can be revoked on the blockchain level by sending a revocation transaction. There's no mechanism for doing this in the current browser. It would cost money to send such a transaction. I'm not sure how (if?) revocation works for subdomains. cc @kantai
They can also potentially be hidden at the browser level:
+1 to this