- From: Henry Story <henry.story@bblfish.net>
- Date: Thu, 29 Dec 2011 23:15:18 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: WebID XG <public-xg-webid@w3.org>
On 29 Dec 2011, at 22:59, Kingsley Idehen wrote: > > I assume, that when you adopt the approach outlined above, you currently end up with verification failures when using the verifiers from Henry and OpenLink? If true, this is a function of the fragment identifier being passed across the wire as part of the HTTP payload generated on the Windows platform, a legacy issue from spec confusion. I'll be improving the test suite on foafssl.org, but right now it's holidays, so I am being more relaxed. I'd recommend people here to do the same and go look at the 28c3 videos, and tell us about good ones. Here's one on TOR and government surveillance systems http://www.youtube.com/watch?v=DX46Qv_b7F4 WebID clearly does not answer the issues they are addressing, but it could at least spread TLS usage to such an extent that blocking TLS would be considered suicidal by bad governments. Henry Social Web Architect http://bblfish.net/
Received on Thursday, 29 December 2011 22:16:00 UTC