Problem with search api

[nyankov]

Hi All,

Does anybody have idea why this url:

http://search.twitter.com/search.json?q=offer OR book OR read since:
2008-04-02 from:nyankov

Give me:

The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.


Any help and advice will be appriciated.

Best regards,
Nikola

[Chris Thomson]

Give this a try:

http://search.twitter.com/search.json?q=book+OR+read+OR+offer+from%3Anyankov+since%3A2009-04-01

-Chris Thomson

[Cameron Kaiser]

> Does anybody have idea why this url:
>
> http://search.twitter.com/search.json?q=offer OR book OR read since:
> 2008-04-02 from:nyankov
>
> Give me:
>
> The page you were looking for doesn't exist.
> You may have mistyped the address or the page may have moved.

I don't think this is likely the explanation, but nevertheless, your URL
is not encoded. I would fix that first.

--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com
-- Evil has middle management? -- 8-bit Theatre #663 --------------------------

[nyankov]

Actualy the url is

http://search.twitter.com/search.json?q=offer+OR+book+OR+read+since%3A2009-01-01+from%3Anyankov

and what I found is that if I change the query to:

http://search.twitter.com/search.json?q=offer+OR+book+OR+read+since%3A2009-04-01+from%3Anyankov

everything is ok since is I try to search for:

http://search.twitter.com/search.json?q=offer+OR+book+OR+read+since%3A2009-01-01+from%3Anyankov

It displays:

The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.

The only difference in both is since date

Any ideas?

On 2 Апр, 15:44, Cameron Kaiser <spec...@floodgap.com> wrote:
> > Does anybody have idea why this url:
>

> >http://search.twitter.com/search.json?q=offerOR book OR read since:

> > 2008-04-02 from:nyankov
>
> > Give me:
>
> > The page you were looking for doesn't exist.
> > You may have mistyped the address or the page may have moved.
>
> I don't think this is likely the explanation, but nevertheless, your URL
> is not encoded. I would fix that first.
>
> --
> ------------------------------------ personal:http://www.cameronkaiser.com/--

>   Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com

[Abraham Williams]

Search only supports since_id: http://apiwiki.twitter.com/Search%20API%20Documentation#Search

2009/4/2 nyankov <nikola...@gmail.com>

--
Abraham Williams | Hacker | http://abrah.am
@poseurtech | http://the.hackerconundrum.com
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[Matt Sanford]

Hi there,

    There is a since:YYYY-MM-DD operator but unfortunately the operators are documented on a different page [1]. Another historical thing, I'll try and find some time to move that stuff over to the API doc [2]. The reason for your error is that the since: date you provided is older than the data currently available. We plan to improve the error messaging when we merge the search and main APIs, so hopefully things will be clearer after that.

    We try to keep as much search data on hand as we can but we're currently limited on disk space. As the rate of tweets increases we need more and more disk to keep old data on hand. We've ordered more disks and await them eagerly. Once those are installed the date range for searches can start growing again. Sorry for the confusing error messaging.

Thanks;

  — Matt Sanford

[1] - http://search.twitter.com/operators

[2] - http://apiwiki.twitter.com/Search-API-Documentation