Re: "Logged in with fedsocweb"

On 7/8/12 11:15 AM, Michiel de Jong wrote:
> On Sun, Jul 8, 2012 at 6:03 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>> For sake of experiment, make yourself a WebID via the service at:
>> http://id.myopenlink.net/certgen .
> yes, i have one, and i like webid in that it's end-to-end, but i think
> technologies like webid and pgp can by definition never be more than
> an option for power users.

Doesn't have to be so. We can simplify the end-user experience, big time!

>
> IMO we should give a default option that can work with a simple-to-use
> user address and password combination, and then describe a power user
> option based on client-side certificates.

That's in place, technology wise, the rest is UI/UX patterns.

>
> as Markus said, the default option should probably be based on the
> OpenID Connect work (which is basically the same as saying it should
> be discoverable OAuth i think - openid and oauth are sort of
> interrelated).

You can't predict the optimal default. Thus, always present options.

> but only saying 'nodes should implement OpenID Connect'
> is not enough to solve these two use cases, i think? Scanning over
> http://openid.net/connect/ i see no explicit mention of friend lists,
> but maybe i didn't read carefully enough?

People just need a (Web|Net)ID. Every Unix user has a user id or userid. 
The Web and Internet are still WANs based on Unix concepts.
>
> Btw, the Lanyrd example is easier to achieve, because it's about who
> you follow, which is something your node can authoratively report on.

"Who" needs to be a verifiable identity. Everything comes after that, 
including who you follow, what you've made, when it was made, where it 
was made, and eventually at chance at subjectively computing: why it was 
made .

> The AirBnb case is about who follow (and thus implicitly endorse) you,
> for which we probably need some sort of signatures? i think this is
> built into foaf?

Nothing to do with FOAF, but everything to do with a verifiable 
identifier protocol such as WebID or NetID (when we go beyond http: URI 
specificity and RDF doc formats).

>
>


-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen