You could hash and sign your data if your game is not written in javascript. That would insure that the high-score submission only was valid when initiated from your code.
On Fri, Apr 30, 2010 at 1:16 AM, Jonny <[email protected]> wrote: > I've been using the Persistence API to store each user's progress in > the gadget (like high scores etc). > The thing is I realized the user has 100% control of his own data. > With a line of JavaScript he can at his own will view all his > currently stored data for a gadget, with another line of JavaScript he > can edit the stored data, and furthermore he can delete all data with > another JavaScript line. > > Is there a way to use the Persistence API to avoid this inconvenience? > I don't want the user to be able to edit his high scores ;-) > > -- > You received this message because you are subscribed to the Google Groups > "OpenSocial Application Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<opensocial-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/opensocial-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" 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.
