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,

Do not use "ands" in your queries.  The default interpretation of
spaces in yr queries is logical AND. And these do count against query

2. The "query" is the q name/value pair. "?q=" (i.e. name q and
proceeding "=") are not counted toward the 140 limit. Everything else
up until the next parameter (delimited by "&") is counted toward the
140 character limited - including the search operators and their
delimiters. Parameters (e.g. rpp), as these are separate name value
pairs, are not part of the query thus not counted toward the max 140
character count.

NOTE: There are exceptions and some overlap that may cause confusion.
For example, Twitter defines "until:" as a search operator while
you'll also see a "&until=" (i.e. "until" parameter) in the queries
generated by the Advanced Search Tool. As a result, both "until:" and
"&until=" are counted toward the 140 max character limit.

The Twitter API is smart enough to see this overlap and recognize what
you are going. However, it isn't documented. So you save you the
trouble, if you are reading this, I'm noting this here.


On Oct 17, 9:52 pm, Scott Haneda <> wrote:
> 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 may be, I just do not know. I hope it is though.
> --
> Scott * If you contact me off list replace talklists@ with scott@ *

Reply via email to