Forwarding Brad's reply to my email.<br>
<br>
>> I'll post to the mailing list when I've got a server working.<br><br>
I've got the yadis client going at <a href="http://foopad.com">foopad.com</a> - hopefully have it
public tonight. There's some cool stuff you can do with the users foaf
file too.<br>
<br>>> The idea looks excellent, although I'd love to be able to use the system to<br>>> give a site permission to write to my metaweblog API. I've got some ideas<br>>> about how this could be added - but it's slightly complex.
<br>><br>>I've been idly thinking about the same sorts of things... grant<br>>permissions along with the assertions or something.<br><br>
One way would be to create a new param on the call to the ID server:<br>
<br>
is_foaf=<a href="http://www.livejournal.com/..../foaf">http://www.livejournal.com/..../foaf</a><br>
has_permission_to=//xpath/to/xml_endpoint/in/foaf/file<br>
<br>
Then when the ID server has confirmed the user wants to let <a href="http://foopad.com">foopad.com</a>
access their endpoint - the ID server sends a message to the xml
endpoint (assuming you control it or can message it) saying 'let
<a href="http://foopad.com/">http://foopad.com/</a> write to the blog'. Then when <a href="http://foopad.com">foopad.com</a> opens a
metaweblog session, it sends the foaf url and a signature signed by the
<a href="http://foopad.com">foopad.com</a> DSA key.<br>
<br>
>> What about sixapart and typekey - are they aware that you're making typekey<br>>> redundant?<br>><br>>I'm pushing for both TypeKey to speak Yadis (trivial, trival addition---<br>>they already do DSA signatures and FOAF files) as well as Movable Type
<br>>being a Yadis consumer and server. (so MT users can be their own identity<br>>authority).<br>
<br>
Sounds great.<br>
<br>
Regards,<br>
Ben<br>