Looking into this.
On Mar 10, 1:36 am, Hrishi 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 to:http://search.twitter.com/search.json?geocode=40.
That feature does not exist yet.
-Doug
On Mar 11, 10:32 am, Lukas Müller wrote:
> Hello,
>
> is there any possibility to search tweets from users that are on list
> xyz/123 (as example ;-)) via the twitter search RSS feed?
>
> Already tried the following queries with no result:
> @xyz/123
> from
There's a bug in the API we just found. We're working on fixing it
ASAP. Thanks for reporting this!
-D
On Mar 11, 5:19 am, amitkr wrote:
> Hi
>
> I am using users/search method to find people on twitter. But the
> order of results does not matches with that of twitters 'people
> find'.
> Moreove
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 wrote:
> Hi dev team,
>
>
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
po
Yes, due to lots of recent growth we're bumping up against some
capacity limits and working on them right now.
In the mean time, some very complex queries will time out. I'd
encourage you to back off on your rates, and please to not
aggressively retry the complex queries that fail [we don't cache
Yes, we do match parts of the expanded URL on searches. That currently
includes query parameters, but we'll be removing that soon.
On May 14, 1:35 pm, Damon Clinkscales wrote:
> Naveen,
>
> I saw a case with one of my searches this morning where a bit.ly url
> appeared to have been expanded befor
Hi Sarah-
This is a bug. We'll be fixing it as soon as possible!
On Jan 22, 1:48 am, Sarah Richards
wrote:
> Hi,
>
> Today I've noticed that the search query I use:
>
> http://search.twitter.com/search.json?q=from%3Aschoolsforhope+OR+from...
>
> Is now also returning Re-tweets of posts, which we
anks for the reply.
>
> Sarah
>
>
>
> On Fri, Jan 22, 2010 at 5:45 PM, twitterdoug wrote:
> > Hi Sarah-
>
> > This is a bug. We'll be fixing it as soon as possible!
>
> > On Jan 22, 1:48 am, Sarah Richards
> > wrote:
> > > Hi,
>
>
We do support max_id in the Search API, though we somewhat discourage
its use, since it queries with max_id are more costly for us to serve
and are frequently used to attempt to abuse our system by
inappropriately and excessively scraping data.
Please be conscientious in its use.
d
On Jan 25, 4:
You should be using search.twitter.com for all search API calls.
On Jan 30, 2:05 pm, Josh Roesslein 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, and trends/weekl
Yes.
-Doug
On Feb 9, 3:27 pm, eco_bach wrote:
> Hi
> I'm confused about the differences in query string parameters if you
> use the advanced search page
>
> vs referencing the Twitter search operators
> pagehttp://search.twitter.com/operators
>
> Are both of the following equivalent?
>
> http:/
12 matches
Mail list logo
