Skip to content
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

Merged
merged 1 commit into from Jul 2, 2017

Conversation

tobiasd
Copy link
Collaborator

@tobiasd tobiasd commented May 6, 2017

No description provided.

@tobiasd
Copy link
Collaborator Author

tobiasd commented May 6, 2017

Eventually this breaks OpenID registration ;-) could not be tested as I don't have openod

@MrPetovan
Copy link
Collaborator

I don't have OpenID either, maybe @strk?

@strk
Copy link

strk commented May 6, 2017

Any GNUSocial instance offers you OpenID. Or use openid.stackexchange.com for testing

@MrPetovan MrPetovan changed the title add token to register [Needs OpenID testing] Add token to register May 7, 2017
@annando
Copy link
Collaborator

annando commented May 12, 2017

Has someone now tested it with OpenID? or should we accept this PR and would see then?

@strk
Copy link

strk commented May 13, 2017 via email

@annando
Copy link
Collaborator

annando commented May 13, 2017

When you don't have any backups, please consider that you mustn't use the same handle again.

@strk
Copy link

strk commented May 14, 2017 via email

@annando
Copy link
Collaborator

annando commented May 14, 2017

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.

@strk
Copy link

strk commented May 15, 2017

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

@fabrixxm
Copy link
Collaborator

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.
If you have a different handle, you can start a new connection process without any problem.

@annando
Copy link
Collaborator

annando commented May 15, 2017

You do have a huge problem with Diaspora. You won't be able to communicate with your handle over Diaspora again.

@tobiasd
Copy link
Collaborator Author

tobiasd commented May 16, 2017 via email

@Quix0r
Copy link

Quix0r commented May 17, 2017

@strk I let database backups run automatically by cronjob. Really easy to accomplish. :-)

@strk
Copy link

strk commented May 17, 2017 via email

@MrPetovan
Copy link
Collaborator

MrPetovan commented May 17, 2017

I also had backups... on the same disk which burned

Now you're scaring me, I don't have offsite backups either :/

@strk strk mentioned this pull request Jun 4, 2017
@annando
Copy link
Collaborator

annando commented Jun 8, 2017

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?

@strk
Copy link

strk commented Jun 8, 2017 via email

@annando annando merged commit 2b16110 into friendica:develop Jul 2, 2017
@tobiasd tobiasd deleted the 20170506-token branch July 2, 2017 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants