[foaf-protocols] Designing the ultimate decentralized login procedure ...
henry.story at gmail.com
Mon Jul 26 13:52:09 CEST 2010
On 26 Jul 2010, at 00:52, Akbar Hossain wrote:
> Not sure if you have seen this.
yes, I blogged about that some time ago
The key piece is showing you that the user is logged in under a
I talked to Azza in London about foaf+ssl at the
privacy workshop a few weeks ago, where we were not given the time
to present, because what we were doing was not API specific. Given the
stuff other people were coming up, I can just assume that that means "too
So I am not sure he really understood what I was talking about, as
I had to give him an overview without accompanying slides.
> So maybe the browser changes not the login form!
The problem with password management only is that you are still left
without a global identity, ie: no linkability.
> Along these lines I can also sort of imagine the following working.
> You install a ceritificate in your browser pointing to your WebID.
> Your browser now has (private) access to a foaf file.
> Possibly hosted privately on your own machine. This file has
> references to your various onlne accounts.
> So now your browser can use your verified webid to select the
> appriopriate login process (form pre-population, etc) depending on
> what service/site you are visiting. In this scenario end user
> adoption is about improving certificate management to get
> access/control of your foaf file.
> Just a thought...
> [ps: I always envisaged openid4.me only taking you to the certificate
> selector and then using the openid directed identity. So the user has
> to do nothing else but select a certificate to log into an openid
> relying party]
> On Fri, Jul 23, 2010 at 8:05 PM, Seth Russell <russell.seth at gmail.com> wrote:
>> Those of you who are trying to design (or evolve into) the ultimate
>> decentralized login procedure may want to imagine how you are changing the
>> state of the art of what is successfully happening on the web today. For
>> that purpose i submit to you the following ...
>> How will that form change? How will it evolve from what it is now to what
>> it will become? I suggest you don't just brush the question aside with a
>> smug, "Well, it will just be one button!" ... that we all can imagine.
>> But, no, we will not get from here to there in just one step. So what will
>> be the very next step that puts WebID on that state of the art login/signup
>> procedure and maintains the maximum compatibility with it? Can anyone mock
>> up such a form and make it work?
>> Seth Russell
>> Alpha testing: tagtalking.net
>> Facebook ing: facebook.com/russell.seth
>> Twitter ing: twitter.com/SethRussell
>> Blogging: fastblogit.com/seth/
>> Catalog selling: www.speaktomecatalog.com
>> Google profile: google.com/profiles/russell.seth
>> foaf-protocols mailing list
>> foaf-protocols at lists.foaf-project.org
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
More information about the foaf-protocols