<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Tom,<br>
<br>
The approach you mention below is more or less a web-of-trust and I
think it to be part of an overall framework. See my previous mail...<br>
Perhaps it's time to setup a Jabber conference between some of the
interested folks.<br>
<br>
<div class="moz-signature">-- <br>
<div><font face="Arial" size="2">Regards</font></div>
<div><font face="Arial" size="2"> </font></div>
<div><font face="Arial" size="2">Signer: Eddy Nigg, StartCom Ltd.</font></div>
<div><font face="Arial" size="2">Jabber: <a class="moz-txt-link-abbreviated" href="mailto:startcom@startcom.org">startcom@startcom.org</a></font></div>
<div><font face="Arial" size="2">Phone: +1.213.341.0390</font></div>
</div>
<br>
tom calthrop wrote:
<blockquote cite="mid:469B0D12.50208@barnraiser.org" type="cite">
<pre wrap="">Hi All,
I appreciate whitelisting will happen and I hope the OpenID foundation
leave this to consumers (effectively creating a blocked list) who will
I'm sure lead to some independent whitelisting service that consumers
can sign up to. I just wanted to throw into the mix another approach
that we are taking from the social networking community....
We will be establishing trust for person A by asking person B to verify
that person A is a human friend (thus vouching for them). This is very
successful in a social networking model.
We will soon have two products; a personal OP with social networking
functionality and our current group collaboration tool (called
AROUNDMe). It will be possible for only people who have been vouched for
to enter an AROUNDMe collaborative space. So we authenticate person A,
then lookup from person B that they confirm trust with person A.
One could argue that this is crackable (person A and person B are both
from <a class="moz-txt-link-freetext" href="http://spam.com">http://spam.com</a>) however we like this model because it follows a
de-centralized approach. One possible approach to this is adding person
B to a verification blacklist if it is found that person B verifies for
spam ID's
On another note, I have asked the OpenID Foundation board to set up a
social networking group (much like a w3c working group), but to date I
have received no reply from them, so were are going to develop this at
<a class="moz-txt-link-freetext" href="http://openid.barnraiser.net">http://openid.barnraiser.net</a> and make all the specs available anyway.
[note AROUNDMe is a GNU package / free software]
tom
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:general@openid.net">general@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a>
</pre>
</blockquote>
<br>
</body>
</html>