Indeed my original suggestion was bong; we don't include an email address in the RDF, but instead a SHA1 hash of their preferred email address. So two comments:
- Does the FOAF RDF spec provide for including real email addresses? We could do this only for logged in users which would minimize spam harvesting.
- If we do fix bug 66105 in the near future (and it is listed as a priority in our 3.0 plan) then that could be extended to allow contacting "the team" through a form in Launchpad. It would avoid an email disclosure issue while still permitting replies to work normally.
Indeed my original suggestion was bong; we don't include an email address in the RDF, but instead a SHA1 hash of their preferred email address. So two comments:
- Does the FOAF RDF spec provide for including real email addresses? We could do this only for logged in users which would minimize spam harvesting.
- If we do fix bug 66105 in the near future (and it is listed as a priority in our 3.0 plan) then that could be extended to allow contacting "the team" through a form in Launchpad. It would avoid an email disclosure issue while still permitting replies to work normally.