On Aug 20, 6:37 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> 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?
--
-ed costello

Reply via email to