The best way to do this is to use the streaming API and catch all the
tweets containing stanley cup when they happen. The search API is
very limited and you will never get more then a couple of thousand
results in the past. Oftentimes much less.
Best regards,
Stefan
--
Twitter developer
1 - Hosted on GAE is probably your problem
you are sharing a limited pool of IP adresses shared by many other
GAE based appls using Twitter API.
see here :
http://groups.google.com/group/google-appengine/browse_thread/thread/20931a508f4dd6e9
happy coding:-)
Nick
http://gaengine.blogspot.com/
Got it. Thanks, Taylor.
On Mar 22, 11:16 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Doug,
We don't have a search result counting API available at this time. One
approach would be to prepare ahead of time and use the Streaming API's track
filter on the URL you're interested
I just wanted to add to this. The 420s have let up for the most part and I'm
no longer seeing rate limiting behavior significantly different from the
norm.
I've noticed that many result pages are coming back with empty results but
if I re-request the same page (after a couple second delay), I can
Taylor,
Yeah this was definitely NOT good.In the past, when there is a
service disruption, your api group would post something on your status
page and tweet about it... Instead, I'm finding out about this from my
customers...
Did y'all tweet about this or present this somewhere where I could
By adjusting the rate limits to reduce the stress on your search api
without notice you have significantly increased the stress level on
our end :P Seriously, advanced notice of the situation would have been
welcome.
In particular what created lots of confusion on our end is that even
after
Hi Augusto,
Thanks for your reply. The problem with the Streaming API is that I'd
have to have set some database app listening to the stream for the
past few years to be able to get all the data (especially for remote
locations). I also don't know where my users are going to be, so I
don't have
Hi Stu,
If you need to use the search API for this, you'll need to tolerate the
greedy-matching on the profile location field, by discarding the results
uninteresting for your purposes (those tweets with no explicit geotagging).
Taylor
On Mon, Mar 21, 2011 at 9:15 AM, Stu
In many cases we are forced to change the rate limits in response to
a significant increase in requests, which means it isn't always possible to
give advanced notice of rate limit changes.
For some of you it sounds like your code that handles rate limiting didn't
react appropriately. When
Without prior notice, I can understand (circumstances), but without
any kind of subsequent announcement?? Means we have to discover issues
ourselves, verify that they're Twitter related (and not internal),
then search around for existing discussion on the topic. Saves us a
lot of time and
We're also seeing 400s on different boxes across different IP
addresses with different queries (so it does not appear to be server
or query specific). These began on all boxes at 2 a.m. UTC. We've
backed off on both number and rate of queries with no effect. We've
also noticed an increase in
We're working to reinstate the usual limits on the Search API; due to the
impact of the Japanese earthquake and resultant query increase against the
Search API, some rates were adjusted to cope better serve queries. Will
give everyone an update with the various limits are adjusted.
@episod
You could use the streaming api and throw away tweets that have no
location data/show them as having a default location.
Whether or not this is a viable option for you depends on how often
the keyword is tweeted and whether you need to index absolutely all
tweets for the keyword...
On Mar 4,
Hi Carlos,
I am not sure I understand the relevance of your question. I am
planning on using OAuth for authentication. The URL count API
(url.api.twit..) does not need authentication.
Assuming that with callback you refer to the Javascript callbacks; The
processing in question will happen in a
are usign oauth api?
in this api your manage the callbacks twitter
On 13 feb, 07:51, Martin Cronjé martincronj...@gmail.com wrote:
Hi there,
I am busy writing an aggregator and I am looking at using the Twitter
API to get URL counts.
I seems that public developers are not allowed to use
We're seeing the exact same problem in our application. We happen to
be using the Twitter ruby gem, but we are experiencing the same
behavior.
-Ryan
On Feb 9, 3:22 pm, chouck cho...@gnipcentral.com wrote:
I've been using curl to access search.twitter.com and recently I've
noticed that
have observed that sometimes some of the keywords get a 420 code? Any
ideas why is this happening?
You get a 420 NOT USED when a search term hasn't been used recently
where the recently is whatever small timeframe (sometimes 7 days,
often less) is currently available in the search index.
I get
Thanks for the reply. So as i understand it i am not being rate
limited, it just doesn't find any results to return for the specific
keywords. In that case should i wait for the amount of time specified
on the Retry-after field to make a new search? If i don't wait will
that lead to my ip getting
Hi Tom,
DataSift is still in closed Alpha but we have enabled a large number
of users within the Alpha to date and will add additional users for
the Beta so if you'd like early access it's well worth signing up on
http://datasift.net and you may find you get in before we launch the
consumer
Hi Sarah,
I'm already a member. Thanks for the offer though :-)
Tom
On 1/4/11 3:45 PM, Sarah - DataSift wrote:
Hi Tom,
DataSift is still in closed Alpha but we have enabled a large number
of users within the Alpha to date and will add additional users for
the Beta so if you'd like early
I just tried to construct a query that searches for users by location,
as it is registered in the location field of their profiles. I had no
luck and it seems this is not possible.
You can also do this using Datasift's FSDL.
✿✿✿ Mohan ✿✿✿
--
Twitter developer documentation and resources:
On 12/29/10 10:40 AM, L. Mohan Arun wrote:
I just tried to construct a query that searches for users by location,
as it is registered in the location field of their profiles. I had no
luck and it seems this is not possible.
You can also do this using Datasift's FSDL.
✿✿✿ Mohan ✿✿✿
DataSift
I just tried to construct a query that searches for users by location,
as it is registered in the location field of their profiles. I had no
luck and it seems this is not possible.
Google find twitter users by location
See localtweeps.com
### Mohan ###
--
Twitter developer documentation and
Also, while it would be possible to use screen names for relations
(i.e. from_user), this would have a very negative side effect.
Mainly, if a user were to change their Twitter account name, previous
relations would be lost.
On Dec 22, 9:44 am, Corey Ballou ball...@gmail.com wrote:
For
I'm sure I came off a little strong in the initial post; unfortunately
for me google groups doesn't supply an edit button. I think there is
still a grain of merit to the request to fix the issue, regardless of
the API being free. I'm interest in knowing the trade-offs of Twitter
essentially
Yeah, well the call to arms may have been over the top. :)
I agree that Twitter should fix the search API. Every time I ask, the
answer is that it will be done eventually, and that it will have
entities and everything else the streaming API has. I think this means
that it will be the streaming
So it must be based on the IP Address and the UserAgent...
I have changed the UserAgent, so it works now, but I don't
particularly like this solution. It would be nice to know what
happened, and what caused it, so I can try to prevent it from
happening in the future.
On Dec 14, 11:24 am, Tom van
UserAgent is 'PivotalVeracity/0.4'
Here's the test script that helped me track down the problem:
[code]
?php
$timeout = 30;
$useragent = 'PivotalVeracity/0.4';
#$useragent = 'Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:
1.9.2.13) Gecko/20101203 Firefox/3.6.13';
$url =
Tested it myself with :
tom-mbp:~ tom$ curl --user-agent PivotalVeracity/0.4
http://search.twitter.com/search.json?q=batteryoperatedcandles.netrpp=100since_id=9431322892177408;
Result :
Same here.
On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote:
About 5 days ago, Suddenly Search API Optional lang had no results..My
optional lang is ko.
Did anybody apply Search API lang option? Did the results come out
correctly?
--
Twitter developer documentation and resources:
And same with some search operators (like source:xxx)
Sorry for posting twice :)
On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote:
About 5 days ago, Suddenly Search API Optional lang had no results..My
optional lang is ko.
Did anybody apply Search API lang option? Did the results
Same problem here. When lang=all is used I am getting results. When a
language is specified I get zero results most of the time, while in
some cases I do get a result. Seems very strange.
On Nov 29, 9:25 am, fbparis fbou...@gmail.com wrote:
And same with some search operators (like source:xxx)
I'm seeing this as well. Including filter:links or setting that language
causes the search to fail. I get an error message saying since_id has been
adjusted due to a temporary error. I'm *not* including a since_id in the
search parameters.
Hayes
On Mon, Nov 29, 2010 at 10:08 AM, Randomness
This has happened before. Appending a since clause works around it,
but limits your search results to only five days. Also last time this
happened they fixed it within a few weeks. I just wish we could get
an official comment on this.
On Nov 28, 5:50 pm, Jeong Hoon Kim redi...@gmail.com wrote:
There is an issue with Twitter's language detection. When specifying a
language (lang=nl) , there is no result, when using lang=all, I do get
results, in my language.
Using lang=all gives us so many results, that we're hitting the rate
limits with lots of stuff we're throwing away straight away
The adjusted since_id to xxx due to temporary error really means
this:
the since_id was not specified so I went back as far as I could.
The earliest tweet is the database was 25075604044 so i used that.
For users who tweet more often this error can still occur but is less
likely. This is
here is my problem
I need to catch some tweets since yesterday 20pm until this morning
8am.
the problem is that there is more than 1500 tweets that I need, and
according to search api docs, I can get a max of roughly 1500 tweets
per search query.
[...]
rpp
The number of tweets to return per
This sort of scenario is better served with advance preparation, rather than
relying on the Search API to excavate the tweets after the fact, it would be
more advantageous to utilize the Streaming API, tracking and storing all
relevant tweets during your period of interest. Is this a one-off task
Matt, thanks for the quick response.
After an evening of trying to figure out what's going on, it appears
to be working again. I guess the problem must have been on my side.
Thank you so much for replying so quickly though, and for the
explanation on rates and error messages!
Many thanks,
ben
Not sure if this matters, but I've tried using no authentication and
oauth authentication for this search API call, and am receiving the
same results for both.
For a while now, I've been tweeting this bug at @twitterapi and
@twitter searching for people who've come across it, and I'm coming
up
I'm going directly to the URL in question; it only seems to happen to
me when I have lang=en anywhere in the url.
On Jun 15, 1:35 pm, Mack D. Male master...@gmail.com wrote:
There seems to be something wrong with thesearchAPI. It is only
returning a tiny subset of what I would expect (after
Can anyone answer my questions??
Matt,
What is exact limit..Whether I can write to twitter for whitelisting
of the IP?
Whether whitelisting of the IP would do any good?
Shan
On Jul 7, 12:16 am, Matt Harris thematthar...@twitter.com wrote:
Hi Shan,
The Search API is anonymous so authenticating makes no difference to the
Shan,
as far as I know twitter has been reluctant to state definite numbers, so
you'll have to experiment and implement a backoff mechanism in your app. Here
is the relevant part of the docs:
Search API Rate Limiting
The Search API is rate limited by IP address. The number of search requests
Thanks for that -- I just figured that out and was coming back to
report my findings, but I guess you beat me to it. :)
On Jun 22, 8:01 am, Jonathan Reichhold jonathan.reichh...@gmail.com
wrote:
There are plenty of results for this, but your url is encoded incorrectly
Hello Twitter,
Anyone home?
j
On Jun 2, 11:28 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com
wrote:
We have a user that is causing us to create a search of the form:
Don SomeLastName
which is returning tweets containing don't and SomeLastName.
Thats a no good!
Is there a decent
Hi Jeffrey,
Thanks for bumping this to our attention. Some of the threads fall off
our radar so a prompt is always welcome.
Search treats separate words as an AND search meaning a search for:
Don SomeLastName
will translate to:
Don AND SomeLastName.
For a complete phrase search you would
Thanks Matt,
Unless they've been updated lately, the docs are not clear as to how
to handle contractions, so thanks for the -don't example.
Given that don't is regarded as a word, we believe that search
should _not_ return don't in a search for don... It's a bug in our
opinion.
Further, I'm not
I've seen the same thing with some of my own searches, and I just
figured the search algo was broken, because it returns results that
have absolutely nothing to do with the phrase you searched for.
On May 26, 6:24 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com
wrote:
So we have customer that
Woops, my bad. I meant a meta search that would make use of all third
party APIs to display the results.
But I got your explanation. So if I intend to process the tweets and
make sense of it, the Streaming API is what I would need to take a
look at. But if I intend to get the search results and
Note that from GAE, your search rate will be throttled significantly,
as you are sharing the Search API with every other GAE project on a
single IP.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Tue, May 4, 2010 at 12:34 AM, nischalshetty
nischalshett...@gmail.com
Oh.. alright.. I thought GAE had multiple IP addresses... hmmm... then
might have to look into Amazon Thanks a lot for the info :)
-Nischal
On May 4, 6:29 pm, John Kalucki j...@twitter.com wrote:
Note that from GAE, your search rate will be throttled significantly,
as you are sharing the
Comcastbonnie confirms this is not unusual:
http://twitter.com/ComcastBonnie/statuses/13083585494
That this error happens for some and not others is not surprising.
With new focus on the Search API this type of issue can be addressed :)
Probably related to this:
http://groups.google.com/group/twitter-development-talk/msg/3af17ba93d66abbf
On Thu, Apr 29, 2010 at 11:52, mikawhite mikawh...@me.com wrote:
Comcastbonnie confirms this is not unusual:
http://twitter.com/ComcastBonnie/statuses/13083585494
That this error happens
This issue is now fixed.
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Thanks, good feedback.
Yep, it is always preferable to be explicit about specifying the
intent. API versioning and explicit options are both good ways of
doing that. The kerfuffle around the popular searches being injected
happened exactly because there was previously no way to specify
intent.
Hi Doug,
I'm getting reports of this from:user delay happening again, so here
are some relevant request/response headers and screengrabs of the
results.
There are some cases where it can be out of sync for up to 8-10 minutes.
This is for the search query from:resourcefulmom
Request Headers
Pretty odd, I am able to use curl to get
http://search.twitter.com/search.json?q=^_^lang=zh
but have the same problem as you fetching it through Firefox/Safari.
On Mar 22, 12:51 pm, Irokez iro...@gmail.com wrote:
http://search.twitter.com/search.json?q=^_^lang=en - works
This is most likely because there are extremely few results in chinese
that match the query.
Right now Twitter Search handles lang queries in a relatively
inefficient way, so that queries for common terms that match extremely
few results may time out. We can (and will) make this better, but the
Hi Chad,
I didn't get there in time, the results looked fine to me. Should you
be able to reproduce this, could you please send more information?
dumps of results would be most useful, with complete HTTP requests/
responses...
best,
doug
On Mar 12, 6:22 pm, Chad Etzel jazzyc...@gmail.com
Looking into this.
On Mar 10, 1:36 am, Hrishi bakshi.hrishik...@gmail.com wrote:
Hello all,
I collecting location based tweets.
I am using max_id and page parameters for pagination.
The ids of the tweets returned seem to be out of order.
For example :
Go
Thank you for your reply!
If this were true then sometimes your request works and other times it
doesn't. Is that the case?
Yes, each time I run my app, it makes ~80 calls to the Search API. I
can only run a full test of the app 2 or 3 times before I get the
Stream Error. But if I run a
Yes, I am receiving limit messages.
I will send an email once my college project is near completion and
ready to go live.
Thanks for Twitter's Dev Team Help!
- Will Mulligan
Worcester Polytechnic Institute
Something just to keep in mind. Try not to postpone integration into a
higher access level stream for last b'coz you might have to process A LOT (I
really mean it!) of tweets. Unless well done it could be over whelming for
the application to integrate with elevated access level stream.
On Tue,
Are you able to tell me how many more?
I know that current am getting about 28 tweets per second that contain
'rt' in them.
I estimated from the twitter.com search, that there are about 40-50
per second, but that is assuming the twitter.com is not limited.
Thanks
If you are using just track predicate, then u should be fine. But in general
gardenhose floods u depending on the time of the day and various other
factors nearly a few thousand tweets per hour on an average or something
similar. But again it depends what u r consuming. My numbers could certainly
Are you receiving limit messages?
If not, than the issue isn't with your Streaming API role, but rather how
you are defining your search terms. You may need a broader predicate set to
catch more of them
If you are receiving limit messages, you can request a higher access level
at
Thanks for the advice. I switched over to streaming and am getting
about 25-30 tweets/sec that contain 'rt'.
Based on main website search, I estimate there are about 45-50 tweets/
sec that contain 'rt'.
So, I am only getting about 50% of the actual tweets. If I applied
for the retweet
both of those are samples -- the streaming API is a sample and the search
API does not return all tweets (not all tweets are indexed by search).
these are the best two options for getting a sample of all the retweets,
unfortunately.
On Sun, Feb 14, 2010 at 11:11 AM, TimeSnag wmulli...@me.com
You should be using search.twitter.com for all search API calls.
On Jan 30, 2:05 pm, Josh Roesslein jroessl...@gmail.com wrote:
Hello,
I have discovered that the search methods search and trends seem to
work okay with the domain api.twitter.com.
But the methods trends/current, trends/daily,
1) Looks like the docs got updated.
2) 400 will eventually just be for API calls that are malformed:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1
Abraham
On Sat, Jan 23, 2010 at 18:40, Andy Freeman ana...@earthlink.net wrote:
(1) When will
(1) When will http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors
be updated?
(2) How does 420 differ from 400?
On Dec 22 2009, 4:19 pm, Wilhelm Bierbaum wilh...@twitter.com wrote:
Eventually the REST API will return the same 420 response code to
indicate rate limiting. We wanted to
1) When will http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors
be updated?
(2) How does 420 differ from 400?
On Jan 23, 4:21 pm, Wilhelm Bierbaum wilh...@twitter.com wrote:
In accordance with our previous announcement, we have completed the change
to Search API rate limiting response
i am getting this response code in my twitter search application, how
to resolve the error ?
On Dec 23 2009, 3:44 am, Wilhelm Bierbaum wilh...@twitter.com wrote:
We're changing the response code sent back by the Search API when the
rate limit has been exceeded. At present, it is impossible to
OK ... next question ... are the rate limit HTTP headers from the REST
API now ported to Search and working / documented?
2. HTTP response headers included in all REST API responses which
count against the rate limit:
* X-RateLimit-Limit the current limit in effect
*
So, any news on the matter. This probably means that the number of
search results has deliberately been reduced to give people an
incentive to move to the streaming api's?
-M
--
Dr. Mikio Braun, Beckerstr. 11, 12157 Berlin
Privat: 030 / 42 10 56 42, Büro: 030 / 314 78627, Handy: 0172 / 97 45
Search results are altered to improve result quality. The Streaming API
exists as a full-fidelity alternative for large-scale integrations.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Wed, Jan 20, 2010 at 3:20 AM, Mikio Braun mikiobr...@googlemail.comwrote:
So,
Dear John,
thanks for the reply. We've already started to look into the migration
to the streaming API. Looks very nice so far!
-M
On Wed, Jan 20, 2010 at 3:41 PM, John Kalucki j...@twitter.com wrote:
Search results are altered to improve result quality. The Streaming API
exists as a
Will you be changing the REST API error code to match the Search API?
RE: 420 = rate limit exceeded.
On Dec 22, 4:44 pm, Wilhelm Bierbaum wilh...@twitter.com wrote:
We're changing the response code sent back by the Search API when the
rate limit has been exceeded. At present, it is impossible
yeah, doesn't make much sense to have two different codes indicating that
the limit is exceeded...
2009/12/23 DustyReagan dustyrea...@gmail.com
Will you be changing the REST API error code to match the Search API?
RE: 420 = rate limit exceeded.
On Dec 22, 4:44 pm, Wilhelm Bierbaum
Eventually the REST API will return the same 420 response code to
indicate rate limiting. We wanted to change as little as possible to
get people comfortable with the new response code.
On Dec 22, 4:07 pm, Marco Kaiser kaiser.ma...@gmail.com wrote:
yeah, doesn't make much sense to have two
@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
I would have to agree with mat. But to each their own. The return
codes frequently make no sense from twitter, so i guess the fact that
it doesn't make sense it is irrelevant, so long as it is consistent.
On Dec 3, 6:29 pm, mat mat.st...@gmail.com wrote:
Given that 400 is bad request, and the
Given that 400 is bad request, and the client SHOULD NOT repeat the
request without modifications (w3.org's emphasis), and 503 means
service unavailable, try again later, and can include a retry-after
header, would it not have made more sense to change the response code
of the REST API to the more
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
hi em.
thanks for the error report, and we'll dig into it further -- but that
seems like it was a transient error. i can, at this moment, hit that
link and it seems to work.
Dear all,
from today Search API's geocode parameter (http://apiwiki.twitter.com/
Except now that I look at it a day later, the results have completely
changed, and seem to be in order.
Why would the results change over time when the same max_id is set,
and was valid at the time of the query? Are the ids of tweets not
generated in ascending order?
On Nov 3, 3:17 pm, TripleM
Apologies for the multiple posts, but as the above links no longer
show the problem, you can replicate as follows:
Go to
http://search.twitter.com/search?rpp=100page=1geocode=-40.900557,174.885971,1000km
Note how long ago the last tweet on that page was posted.
Click 'Older' at the bottom.
I'm experiencing the same. Empty results from the Search API when
using the since_id parameter.
This is really bad and my users are complaining about the Saved
Searches tabs not updating.
If you're lucky you end up at a caching server with up-to-date
information, but it seems as if you can't
1 - 100 of 215 matches
Mail list logo
