--
You received this message because you are subscribed to the Google Groups "foaf.me" group.
To post to this group, send email to foa...@googlegroups.com.
To unsubscribe from this group, send email to foafme+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foafme?hl=en.
This is exactly why re-authentication (login) to a website or service with your WebID should not be dependant on verification of the certificate in the profile document.
It's also, unfortunately, one of the reasons that i won't use WebID now for my sites or my identity.
My point is not that there is some little transitory bug over at openid.me and the pain it causes ... my point is that the protocol has been defined so that it is inherently and needlessly unreliable. It is dependent on the site which issued the WebID to be up and running. But it doesn't need that dependence! Login using WebID need only be a transaction between the website and the client's browser.
I haven't touched my foaf.me profile for months, and in the middle of
that period is when openid4.me stopped working.
> I checked your profile with rapper and can't be parsed.
Works for me, rapper returns 15 triples with no errors.
--
Nicolas
Sorry to herar you having issues.
Would you mind trying the following url.
https://openid4.me/tools/simpleLogin.php
To check your certificate first.
Thanks
2010/9/11 Nicolás Alvarez <nicolas...@gmail.com>: