3 ms·
If it were a verification badge you’d think someone would develop a technology to sign tweets / posts the same way you can sign and push a git commit, i.e. , th
by vonseel 4y ago
If it were a verification badge you’d think someone would develop a technology to sign tweets / posts the same way you can sign and push a git commit, i.e. , the authentication backend would incorporate some sort of signing which requires a special token.
All this would have to be hidden from the end-user, of course, so I’m not sure what it offers on top of just knowing the user credentials.
Maybe it would have to be implemented where when you login to an app, the app also looks in iCloud or Google storage for the keys associated with your verified identity (which you have to submit documents for, and when submitting documents, your phone creates the keys). Any additional devices the user wishes to use, he or she would have to share the keys from the initial device.
Not a crypto guy, is this the gist of what actual verification would look like and what additional benefits it serves over 2FA or knowing the users password?
- charcircuit 4y agoIt's called having an account. If you see a post from @asdf then the post came from @asdf. No one else can make posts as @asdf.
- vonseel 4y agoWhat about if someone pretending to be @asdf makes an account with his name? Or, if he is hacked? Both of these seem like reasonable problems to solve with a verification or signing service. One is solved by verifying the identity of the user once, while the other would be more like each git commit.
- charcircuit 4y agoOny one person is able to own @asdf. If you are hacked you can be impersonated in any scheme.