@AJ Chen
You are 100% correct when you say that it’s the user’s responsibility
to clean up duplicates in the search results. My issue is not so much
about there being duplicates, but the fact that there are so many of
them. My concept of search is that if there have been new tweets
posted, say 30
unless I miss something, it's usually user's responsibility to dedup
returned tweets on the client side. if you see duplicates between two feeds,
just remove the duplicates. this is what client application should have in
any case.
if you see no fresh tweets but only old tweets, there may be a
Hi, Raffi
Were you able to raise the cache issue with the search team?
Seems the problem is worse than I thought. I have run my script
(getting 25 results from search every 15 minutes, for Mumbai) for two
days. The first day had 71% duplicate results due to the caching
issue, while the second day
@Abraham
I actually use the geocode with the search api for my script, so using
the search api isn't my problem. My problem is that I get stale
results from the search cache, even when querying after a sufficient
interval. Also the stale results seem hours old (at times, in fact
yesterday at 23:00
unfortunately, there is no (current) way to subscribe to the streaming
API for a particular location. as for the caching issue on the
search, that's unfortunate, and i'll try to raise the issue with the
search team next week.
@Abraham
I actually use the geocode with the search api for my
the streaming API would be ideal for my purposes, so will eagerly wait
and see what new features the twitter api dev team adds before the
final release. Till then, search api is what I will use. Thanks a lot
Raffi, for trying to raise the issue with the search team.
Regards,
Elroy
On Nov 28,
I got some requests to post the query that I am using:
here is the query :
http://search.twitter.com/search.atom?geocode=19.017656%2C72.856178%2C15.0mirpp=25
Do correct me if I am not querying or using the API correctly. (Should
have been my first question actually :) )
Also here is a sample of
Hi Elroy,
I tried your query from python several times within the same minute.
After running the query several times in a row I start getting fresh
results and they remain fresh for a while. I tried changing the least
significant decimal to make it a different query and I get stale
results
Hi Everyone,
I've been running my script as a cron task (every 15 minutes) since
last evening. So far I've got about 1375 results logged, out of which
973 are duplicates (meaning stale entries)...a staggering 70.7076%
or approximately 71%. This is way more than expected..so a shout out
to the
Just a couple of queries: I'm using the Atom format for search results
(As mentioned on http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search)
.
I get the published date in the atom feed. So I am not sure what you
mean by created_at:Fri, 27 Nov 2009 00:06:44 +. The format
available
@Raffi, thanks for the reply. I now convert the time from UTC to my
local time zone, so my time zone problem is sorted out. On the issue
of search, been going through the streaming api docs. From what I have
gone through so far, there doesn't seem to be a way to query for
status updates from a
On Fri, Nov 27, 2009 at 12:38, enygmatic enygma...@gmail.com wrote:
From what I have
gone through so far, there doesn't seem to be a way to query for
status updates from a certain geographical location, say limited to a
city. I may be mistaken here, so do correct me if I am wrong.
Check out
@Raffi,
Thanks for the info.
Just a couple of queries: I'm using the Atom format for search results
(As mentioned on
http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search).
I get the published date in the atom feed. So I am not sure what you
mean by created_at:Fri, 27 Nov 2009 00:06:44
13 matches
Mail list logo
