W3C home > Mailing lists > Public > public-wiki-dev@w3.org > October to December 2007

RE: FOAF + OpenID Re: Spam protection for MediaWiki

From: Rotan Hanrahan <rotan.hanrahan@mobileaware.com>
Date: Tue, 6 Nov 2007 13:49:53 -0000
Message-ID: <D5306DC72D165F488F56A9E43F2045D3015983A2@FTO.mobileaware.com>
To: "Tim Berners-Lee" <timbl@w3.org>, <public-wiki-dev@w3.org>
Cc: "Joe Presbrey" <presbrey@mit.edu>, "Danny Weitzner" <djw@w3.org>, "Lalana Kagal" <lkagal@csail.mit.edu>, <danbri@w3.org>

Maybe Dan (copied) could give us some technical advice from his own
experience [1][2] with implementation of the approach in MediaWiki. Then
the hackers can get to work...


[1] http://danbri.livejournal.com/
[2] http://wiki.foaf-project.org/Special:OpenIDLogin

-----Original Message-----
From: public-wiki-dev-request@w3.org
[mailto:public-wiki-dev-request@w3.org] On Behalf Of Tim Berners-Lee
Sent: 06 November 2007 13:36
To: public-wiki-dev@w3.org
Cc: Joe Presbrey; Danny Weitzner; Lalana Kagal
Subject: FOAF + OpenID Re: Spam protection for MediaWiki

Please consider FOAF   + OpenID.

See http://esw.w3.org/topic/FoafOpenid

The DIG blog uses this.  There is a stand-alone python script which  
produced a whitelist, which is fed to the blog engine.   So MediaWiki  
would need  to be able to take a whitelist of OpenIds.

This uses the social network for figuring out who to trust. You  
could, for example, allow anyone who is a friend of a friend of a  
wokring group member to post a comment.

The seed set and the path could be altered as necessary to allow a  
wide group of entry. It leaves us open to decide what the criterion  
is for being able to edit things.

It also has the advantage that we get name and home page for users.   
The blog doesn't use those yet, but the interface would be better if  
it did.

Received on Tuesday, 6 November 2007 14:05:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:40:57 UTC