I have suggested previously that the capability of an application to geo-code a users tweets and the capability of an application to opt-in to geo-coding for a user be made OAuthorizable.
The application would request these capabilities when registering. If twitter didn't trust the application, it wouldn't grant them. If an application were granted those capabilities when registering, then when a user signed in with OAuth for that application they would be allowed to either authorize the application to use them or not. Thus, the user interface would be made more complicated only for applications that needed it. I think this proposal is a reasonable compromise between twitter's and users' concerns and developers desires. Comments? Jim Renkel On Sep 29, 1:47 am, Abraham Williams <4bra...@gmail.com> wrote: > My understanding is Twitter wants the opt-in to be explicitly done by the > user. If it is changeable through the API apps could enable it without the > consent of the user. > Abraham > > On Mon, Sep 28, 2009 at 13:03, CodeWarden <paul0...@gmail.com> wrote: > > > Hello, > > > Really looking forward to the ability to include lat/long with > > tweets. However, since all of my users are on mobile devices, it > > would be most useful if they could change the geo_enabled flag via the > > API. Before you enable this capability could you allow the update > > profile method to also update the geo_enabled flag? > > > -Paul > > -- > Abraham Williams | Community Evangelist |http://web608.org > Hacker |http://abrah.am|http://twitter.com/abraham > Project |http://fireeagle.labs.poseurtech.com > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, WI, United States