New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Needs OpenID testing] Add token to register #3439
Conversation
Eventually this breaks OpenID registration ;-) could not be tested as I don't have openod |
I don't have OpenID either, maybe @strk? |
Any GNUSocial instance offers you OpenID. Or use openid.stackexchange.com for testing |
Has someone now tested it with OpenID? or should we accept this PR and would see then? |
My node is down (disk failure) and I dunno when I'll have time to
bring it back up (btw, will need to re-do all my connections, as
I didn't take any backup).
|
When you don't have any backups, please consider that you mustn't use the same handle again. |
Why is it so ?
|
Every handle has got a unique private and public key pair. The private one is stored only on your machine, the public one is stored at every of your communication partners. When you now want to contact anyone that has contacted you before, the public key will not fit to your new private one. So the communication will fail. It's a pity that you don't have any backup. The solution is to use another subdomain and/or nickname. |
Wow, this is really unfortunate. A liberating technology should also free us from annoyances, and this is a HUGE one :) For comparison: Kontalk warns your contacts about you having changed your key and gives them a way to (1) avoid encryption (2) confirm new key. Yes, it's a pity I didn't take backup, but even bigger pity that loosing my keys makes my global handle unavailable forever. One day all handlers will be taken forever :P |
The handles aren't taken forever. You can reuse it, but you must inform all your contact to remove you via some other communication channels, before reconnect to them. |
You do have a huge problem with Diaspora. You won't be able to communicate with your handle over Diaspora again. |
On Mon, 15 May 2017 09:44:04 -0700 Sandro Santilli ***@***.***> wrote:
Yes, it's a pity I didn't take backup, but even bigger pity that
loosing my keys makes my global handle unavailable forever. One day
all handlers will be taken forever :P
Isn't this only a problem for communication over the Diaspora protocol?
|
@strk I let database backups run automatically by cronjob. Really easy to accomplish. :-) |
I also had backups... on the same disk which burned
|
Now you're scaring me, I don't have offsite backups either :/ |
Can we now accept this PR? Since this is now an early development stage we should habe enough time to see if something breaks, don't you think so? |
Go ahead, I cannot test anyway. I've been set off by the identity-burn bug
|
No description provided.