> > Users will need to come to the website to change the setting. If we > > provided an API, a misbehaving application would change the setting > > without the user knowing - hence the read-only attribute. > > Perfect, that_s what I_d expect. But I throw this out anyway: once > someone has opted in, would you consider adding an API method to allow > geo to be turned on/off? Or would you expect the individual > applications to allow users to mask their location when posting a > tweet?
Even so, though, I don't think that would fully get around the malicious application problem unless you could say *which* apps got to turn it on and off, and even then ... -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- /etc/motd: /earth is 98% full. please delete anyone you can. ---------------
