- From: Henry Story <henry.story@bblfish.net>
- Date: Fri, 15 Jul 2011 00:29:26 +0200
- To: WebID XG <public-xg-webid@w3.org>, Ben Adida <ben@adida.net>
I am CCing Ben Adida who posted some interesting information on Browser ID. For a general view: https://browserid.org/ For detailed technical overview http://lloyd.io/how-browserid-works It is pretty close to what WebID does I think, except that they omit the TLS part, though they re-invent it using javascript - a bit like what Manu Sporny was working on. It removes the need for TLS but requires a browser extension to work - I gather on first reading. Since Mozilla is putting it forward I suppose that could work -- though it will take time for browsers to ship with all of this. If they could use the same keychain used by TLS and have both BrowserID use the same keys linked to the certificates WebID uses then the two could work nicely together perhaps. So if a Relying party could provide TLS - which I think more and more will with DNSsec and DANE rollout - then the certificate route could be used. For servers that did not have TLS, then this would be the better solution for a long time. In any case the UI remarks I made at the end of the video on http://webid.info/ are still needed in both cases. Henry Social Web Architect http://bblfish.net/
Received on Thursday, 14 July 2011 22:30:08 UTC