Raffi:
Thanks, that helps a great deal, we have created an app that our
business customers want to use, we will start testing with #94109
etc...and let you know when we go live, hopefully you guys will
release the geolocation soon. Abir
On Sep 17, 4:04 pm, Raffi Krikorian wrote:
> hi abir.
>
>
hi abir.
It's not yet live on Twitter - when it does become live, there will be
a setting available under each user's settings page to turn on the
ability for his or her API clients to annotate tweets.
On Sep 17, 2009, at 6:38 PM, Abir wrote:
Guys:
I am confused. Is the Geolocation
Guys:
I am confused. Is the Geolocation now available on the API?
How are users opting in to it on a tweet basis? or is the user
release later on?
Thanks,
Abir
On Sep 9, 7:13 pm, Mark Mason wrote:
> For those using the iphone and tweetdeck, you can click the locate
> icon and your iPhone:
For those using the iphone and tweetdeck, you can click the locate
icon and your iPhone: Long:Lat is updated on your profilie.location.
I am interested in GEO locate, so products can find you.
Example, You are on interstate driving or passenger, and it is after
3am, and you tweet...
Holiday Inn
hi jim.
that's definitely interesting - i don't think this will make it into
the first release, but i like the per-app permissions notion based on
oauth. it fits well on the "grant permission read" or "grant
permission write" options in oauth in general.
Raffi,
I fully understand the
Raffi,
I fully understand the concern about privacy. To that end, here's
something you may want to consider:
Have application / web-site "over-rides" of the geo-code enable be
another option on OAuth. This way a user can control the creation of
geo-coding in their tweets on a finer grain basis.
Thanks Raffi, appreciate the info.
Abir
On Sep 3, 9:09 am, Raffi Krikorian wrote:
> hey abir.
>
> > Great discussion, thegeolocationcode is exciting opens up so many
> > possibilities.
>
> thanks! we're excited as well.
>
> > 1. Would you guys consider thegeolocationcode, opt-in on a tweet
> >
Behalf Of Raffi
Krikorian
Sent: Wednesday, September 02, 2009 18:01
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: if you will be using the Geolocation
API ...
hi jim.
yup!
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verif
y_credentials
Raffi
hey abir.
Great discussion, the geolocation code is exciting opens up so many
possibilities.
thanks! we're excited as well.
1. Would you guys consider the geolocation code, opt-in on a tweet
basis? It would be an optional input on a tweet basis with the
default=off; This way users can cho
: [twitter-dev] Re: if you will be using the Geolocation API ...
hi jim.
yup!
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verif
y_credentials
> Raffi,
>
> Another question came up as I was thinking about support for this in
> my web-site (http://twxlate.com):
>
>
Raffi:
Great discussion, the geolocation code is exciting opens up so many
possibilities.
1. Would you guys consider the geolocation code, opt-in on a tweet
basis? It would be an optional input on a tweet basis with the
default=off; This way users can choose, "Hey, I am walking down
market str
hi jim.
yup!
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials
Raffi,
Another question came up as I was thinking about support for this in
my web-site (http://twxlate.com):
Will the elements returned in the responses to API requests
include information
Raffi,
Another question came up as I was thinking about support for this in
my web-site (http://twxlate.com):
Will the elements returned in the responses to API requests
include information that indicates whether or not the user has opted-
in to geo-coding of their tweets?
I would like to see
> unfortunately not. as we're pretty sensitive to our user's privacy,
> for now, a user will have to go to twitter.com with a browser to turn
> on the setting (remember, by default it is off).
I think this is very wise, but I might suggest that there be an API exposed
method to turn geolocat
hey jim.
1. "the user.location is a completely separate entity (for now)"
implies
that maybe sometime in the future it may be used, e.g., to provide a
default geo-coded location for a tweet. I would suggest that if the
user's profile location if ever geo-coded, that geo-code should be
added
esday, September 01, 2009 17:20
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: if you will be using the Geolocation API ...
> My understanding is that all tweets will contain geo-location
> information: if the information was supplied when the tweet was
> create
My understanding is that all tweets will contain geo-location
information: if the information was supplied when the tweet was
created,
that will be used; if no information was supplied, then the "default"
location from the user's profile will be used.
actually - if there is no data passed i
o: Twitter Development Talk
Subject: [twitter-dev] Re: if you will be using the Geolocation API ...
My iPhone app ( http://myallo.com/hotlist currently waiting for Apple
approval to go into the App Store) periodically wants to tell Twitter
the user's location. If the user is in motion, and
My iPhone app ( http://myallo.com/hotlist currently waiting for Apple
approval to go into the App Store) periodically wants to tell Twitter
the user's location. If the user is in motion, and the app is open, as
often as every 5 minutes. But it doesn't want to tweet it ("I'm here",
"Now I'm here",
hi nicole.
Also I am surprised that the geolocation of the person can be attached
to the tweets but still not to the profile - something which would
make
location based services so much easier, even without having each
tweet tell the world where you are?
part of our hopes when we designed
20 matches
Mail list logo
