March 4, 2009 at 09:212 ways to unified identification, and both Jabber
Do we want a single registration - yes, of course.
“Let's centralize registration” - which could be simpler and ... more limited.
Firstly, I have to register (register anyway!) On the provider's website.
Secondly, remember another username and password.
Thirdly, enter this username and password.
- ancient dull search and matching of 2 keys in the database. It's just that the bases now intersect (by the way, I think there are problems with this).
Fourth, openID might look like this “pretty”: technorati.com/people/technorati/username
E-mail
Funny, most of the options for obtaining openID themselves require identification - by email.
E-mail has long been the core of any identification, as the author of the article, Instant Mail and Life Without Passwords , correctly noted .
And again, I correctly noticed that the mail interface is inconvenient for authorization on the site. So something else is needed, and this is Jabber.
almost the only popular open protocol. Openness allows you to use it in your applications. You can talk as much as you like about the problem of switching ICQ users to jabber, but it’s high time to understand that jabber is a promising technology for building text-command interfaces (hereinafter JCI ), and ICQ, Skype and other closed protocols are nothing more thangeneral insanity :) social misunderstanding.
So it's time to turn jabber into an authorization standard. It already exists and is being used - you can feel it at http://juick.com/ .
- this is what should become the norm (in terms of ease of access).
It is worth noting that juick uses a radical approach: only JCI, and the web interface is completely absent, respectively, and authorization on the site is not needed here.
We are used to the web interface. JCI is good, perhaps when developing clients, we no longer need a web interface, but now we need it (in places). The jabber authorization algorithm is very simple.
0. Add a contact (for the first time).
1. We send a command for authorization from jabber (preferably common for all servers *, for example WI)
2. A link comes from the jabber server.
3. We follow the link, the server opens access to the web interface.
No registration, no passwords, and access to the web interface is obtained.
This is a different authorization method, it is not based on matching 2 keys from the database.
The second option (there are two of them in the title of the article) is the reverse of the first one - an authorization request from the site (enter the JID), and confirmation in the jabber.
I personally like the first way, because it eliminates the need to refuse authorization if someone decides to hack your account.
What do we have
openID
“Let's centralize registration” - which could be simpler and ... more limited.
Firstly, I have to register (register anyway!) On the provider's website.
Secondly, remember another username and password.
Thirdly, enter this username and password.
- ancient dull search and matching of 2 keys in the database. It's just that the bases now intersect (by the way, I think there are problems with this).
Fourth, openID might look like this “pretty”: technorati.com/people/technorati/username
Funny, most of the options for obtaining openID themselves require identification - by email.
E-mail has long been the core of any identification, as the author of the article, Instant Mail and Life Without Passwords , correctly noted .
And again, I correctly noticed that the mail interface is inconvenient for authorization on the site. So something else is needed, and this is Jabber.
Jabber!
almost the only popular open protocol. Openness allows you to use it in your applications. You can talk as much as you like about the problem of switching ICQ users to jabber, but it’s high time to understand that jabber is a promising technology for building text-command interfaces (hereinafter JCI ), and ICQ, Skype and other closed protocols are nothing more than
So it's time to turn jabber into an authorization standard. It already exists and is being used - you can feel it at http://juick.com/ .
- this is what should become the norm (in terms of ease of access).
It is worth noting that juick uses a radical approach: only JCI, and the web interface is completely absent, respectively, and authorization on the site is not needed here.
We are used to the web interface. JCI is good, perhaps when developing clients, we no longer need a web interface, but now we need it (in places). The jabber authorization algorithm is very simple.
0. Add a contact (for the first time).
1. We send a command for authorization from jabber (preferably common for all servers *, for example WI)
2. A link comes from the jabber server.
3. We follow the link, the server opens access to the web interface.
No registration, no passwords, and access to the web interface is obtained.
This is a different authorization method, it is not based on matching 2 keys from the database.
The second option (there are two of them in the title of the article) is the reverse of the first one - an authorization request from the site (enter the JID), and confirmation in the jabber.
I personally like the first way, because it eliminates the need to refuse authorization if someone decides to hack your account.