So the conclusion is:
1. DO NOT use the search operators that appear in the queries
generated by the Twitter Advanced Search tool. For example,
http://search.twitter.com/search?q=ands=
Do not use ands in your queries. The default interpretation of
spaces in yr queries is logical AND. And
Still waiting for a response here. I tried a query with the Twitter
Advanced Search tool:
And still waiting on a response. More information from a associate:
Subject: Re: Do you know what is being counted toward query length
Yeah, because your using twitter search and not api!
An Api String would be
For Geo Locations
You do realize that Twitter's employees take the weekends off, too, just
like the rest of us? Please don't bump threads.
On Sat, Oct 17, 2009 at 20:39, leonspencer spencer_l...@yahoo.com wrote:
And still waiting on a response. More information from a associate:
Subject: Re: Do you know what
Do NOT respond or post to this thread unless you can answer the
question. And no, I am not bumping threads.
Get a life.
Leon
On Oct 17, 8:35 pm, JDG ghil...@gmail.com wrote:
You do realize that Twitter's employees take the weekends off, too, just
like the rest of us? Please don't bump
I am not sure I understand the confusion, the API is 140 characters
exactly in the query string. You can run this, don't run it often, or
put a sleep 1; in the loop if you do.
#!/bin/bash
# This script assumes you pre url encode your data.
# Request url
Continuing to go it along with the Advanced Search Tool to see what
defines the query and length of 140 chars. Latest try resulted in
the following response from the tool:
You must enter a query.
This is the query I entered from using the advanced search tool:
Thank you for your response. I'll run the lines to look at this further. The
confusion is as whether Query string refers to HTTP query string (? until
end) or the Twitter API query (?q=value) value w/operators and parameters?
Usage Notes:
* Query strings should be URL encoded.
I believe Query string is everything after the q=, not including the
= of course. So no matter how it is encoded or not, you just count up
the chars, and that should be all you get. It is somewhat limited,
but I do not think entirely designed to do massively complex queries.
I used to
Thanks Scott. Thats what another associate was suggesting last night. I figured
the Twitter Advance Search Tool was wrapping around the Api and I could plug
its queries into curl. I guess that is not the case.
Thank you
From: Scott Haneda
Yes, it seems a bit of a mess, but rely on the API, and the responses
it gives you. The web based advanced search is a nice way to do a
quick visual test, but as you have seen, can spit out some bizarre
things.
I think the bash script will help you definitively answer anything you
need
I brought that up the other day, twitter eating their own dog food,
to which I was told they do, but only in some parts. It would be nice,
so that when the API is down, twitter is down, and we as developers
did not look like our apps suck, but that may not be a goal for
twitter, or it
12 matches
Mail list logo
