My question is if there will be any plans for a whitelist of apps to
allow for persistent geo information?
I post travel tweets and would love to post them with the geo info of
the location, not necessarily where I'm at. In this case persistence
would be beneficial for people who search and find
ah, yes - most certainly. @rsarver will be putting together a list of
"best practices" around geo, but, most certainly, you could just store
this locally.
Right, and I see where Twitter's coming from. I'm speaking more to
API consumers that wish to persist the API/Geocode data on their own
Right, and I see where Twitter's coming from. I'm speaking more to API
consumers that wish to persist the API/Geocode data on their own systems.
On Tue, Sep 29, 2009 at 12:19, Raffi Krikorian wrote:
> its not a matter of caching the tweets, per se - its a matter of storing
> extremely sensitive
its not a matter of caching the tweets, per se - its a matter of
storing extremely sensitive information for the long haul. we intend
to provide this information on a long-lived-basis at some point, but
until we have better privacy mechanisms in place, we are not going to
be storing this in
hi jim.
As an alternative to a hard coded 7 days for the interval to the
removal of geocoding information from a tweet, I suggest that an
optional "expires" parameter be added to the statuses/update method.
The value of this parameter would give the number of days between the
tweet creation and
I assume you're caching the tweets in a local DB or something in order to
provide histories of > 3200 tweets. For now, can't you also just cache the
geocode info?
On Tue, Sep 29, 2009 at 12:11, jim.renkel wrote:
>
> As an alternative to a hard coded 7 days for the interval to the
> removal of ge
As an alternative to a hard coded 7 days for the interval to the
removal of geocoding information from a tweet, I suggest that an
optional "expires" parameter be added to the statuses/update method.
The value of this parameter would give the number of days between the
tweet creation and when the g
I just noticed this in the API wiki, under the statuses/update method:
"Currently, all geolocated information will be removed after seven
days."
Two questions:
1. What exactly will be removed: the geocoding attached to the tweet?
Or the whole tweet?
the geocoding attached to the tweet.
