[foaf-protocols] working on the logout problem
henry.story at bblfish.net
Fri Sep 3 00:17:17 CEST 2010
On 2 Sep 2010, at 22:00, Nathan wrote:
> Henry Story wrote:
>> I have filed the following bugs:
>> Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=593066
>> Chromium (OSX) latest (sept 2): Interestingly here just resetting the session gets Chromium to ask you for a new certificate. I wonder if that is a good idea, or if that is not perhaps too fragile. Should I file a bug here?
> IMHO too fragile, realistically we need an ID manager in the user agents that allows people to:
> (1) select a certificate
> (2) offer an option to remember which certificate to use for X address or all address
Safari does that. With the logout working, Safari could end up being the best browser around, oddly enough.
> (3) forget which certificate to use from (2)
yes. See the two bug reports below.
> Anything in between is pretty much just a hack, and afaik only (1) is covered so far.
Well this has to be part of the browser. So we need to fill in bug reports for that, and get people to vote for them. If one browser does the right thing, the others will soon follow, especially as we get towards the 100 thousand webid actively used.
We have this but for Firefox
I reported an issue with apple too, and for Opera, that follows pretty much what I explain in the last note I put in the above two issues.
Any other fix is a hack. But for the moment we are limited to hacks. If we can get a good community going with those hacks, then it will be easy to entice the vendors to do the right thing.
Having the server send a logout message is a fallback option too. We just need to work on collecting these and adding them to our software. Perhaps also the flash solution can help, but it needs to be tested much more carefully.
Social Web Architect
More information about the foaf-protocols