Or it should have a built-in method for privacy control with a server-side boolean parameter, allowing anonymous navigation. Or people could create fake accounts. =)
Cheers, Robson Eisinger. As far as I know, that also reduces the use of fake accounts On 11/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > http://code.google.com/apis/opensocial/terms.html > > The OpenSocial terms refer to this issue, however one could easily > enough upload the same privacy-invading XML file to their server with > a different name, add it as an app and start harvesting emails again. > > I think Facebook has a setting to stop apps reading your data; a > similar system could be implemented for OpenSocial, and then > developers would have to use the provided Orkut etc. tracking widgets. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
