[OpenID] [foaf-protocols] Lack of browser support

[SitG Admin]

>If it is not a problem that the information be public then this is very nice.

Could it be encrypted in the FOAF file, and the user supply a 
separate (decryption) password to authorized parties directly? It 
would impose an extra burden on the user (though their 
clients/blackberries could presumably be made to store all of their 
passwords for them), but if they want that added layer of privacy - 
well, optional "Security on these clients requires user reciprocation 
to complement our efforts."

-Shade