4 ms·

I don't think you should take it as a given that decentralization of login is good. I do not want my credentials stored on every personalized web site that I go

I don't think you should take it as a given that decentralization of login is good. I do not want my credentials stored on every personalized web site that I go to, so appreciate when I can sign in with one of my existing ids.

EGreg 10y ago
It doesn't have to work that way. You choose which domain you'd like to be responsible for holding your identity and address book, and then choose to authenticate with some domains and host some of your data on them. Those domains each get a different user id from your identity server, which knows all your user ids on each of those other domains. Now you have a bunch of ids in different communities but no one except the server you trust has to know what they are. Thanks to 3rd party cookie policies, you can't easily be tracked across domains either. Only the people who you want to share your ids on other services with will know. Such as your friends. You might tell only a few people that you are CrackerJack on porn.com, but you might tell everyone that you are FooManChu22 on Instagram. It's all up to you. And it should be seamless and automatic – when you arrive at a new service, you should already have the ids of all your friends on that service who shared it with you by now. You send this list to the service in order to connect with those friends. And you can also get notifications when a friend joins a service. This is truly decentralized, private, secure, and social. Here's a diagram: https://qbix.com/diagrams/groups.png https://qbix.com/diagrams/groups.png And if you want to learn more, go here: https://qbix.com/platform https://qbix.com/platform or email me.
- candiodari 10y ago
  All that telling people sounds like a lot of work. Also how does discovery work ? All these approaches seem to push nothing by default but that's not that useful.

4 ms·

I don't think you should take it as a given that decentralization of login is good. I do not want my credentials stored on every personalized web site that I go

by ec109685 10y ago

EGreg 10y ago
It doesn't have to work that way. You choose which domain you'd like to be responsible for holding your identity and address book, and then choose to authenticate with some domains and host some of your data on them. Those domains each get a different user id from your identity server, which knows all your user ids on each of those other domains. Now you have a bunch of ids in different communities but no one except the server you trust has to know what they are. Thanks to 3rd party cookie policies, you can't easily be tracked across domains either. Only the people who you want to share your ids on other services with will know. Such as your friends. You might tell only a few people that you are CrackerJack on porn.com, but you might tell everyone that you are FooManChu22 on Instagram. It's all up to you. And it should be seamless and automatic – when you arrive at a new service, you should already have the ids of all your friends on that service who shared it with you by now. You send this list to the service in order to connect with those friends. And you can also get notifications when a friend joins a service. This is truly decentralized, private, secure, and social. Here's a diagram: https://qbix.com/diagrams/groups.png https://qbix.com/diagrams/groups.png And if you want to learn more, go here: https://qbix.com/platform https://qbix.com/platform or email me.
- candiodari 10y ago
  All that telling people sounds like a lot of work. Also how does discovery work ? All these approaches seem to push nothing by default but that's not that useful.