[twitter-dev] Re: search.rss

2009-05-28 Thread davidzimm
I am migrating my app from rss to atom and realized something- a problem I thought was limited to rss occurs with atom as well. Here's the problem: sometimes, even within a matter of minutes, a feed loses the latest item and then gets it back. This is supremely annoying. I thought switching to

[twitter-dev] Re: search.rss

2009-05-27 Thread Matt Sanford
Hi Jonas, It is not safe to use and will go away at some point. It was added for questionable reasons and has never been linked to or documented. Having said that I don't remove it because people have changed .atom to .rss and started relying on it. Please don't use it since it has

[twitter-dev] Re: search.rss

2009-05-27 Thread Jonas
Matt, Okay, I'm switching back to search.atom. However, I still get an Invalid Parameter error when since= is not empty. Are all the parameters that are available to the search command also available to the search.atom command? Jonas On May 27, 3:41 pm, Matt Sanford m...@twitter.com wrote:

[twitter-dev] Re: search.rss

2009-05-27 Thread Jonas
Hi Matt, I mistakenly wrote since= above when I meant to write near=. The following url should return tweets with 15 miles of nyc, but instead I get invalid parameter.

[twitter-dev] Re: search.rss

2009-05-27 Thread Chad Etzel
near is not supported in .rss, .atom, or .json feeds for search (is said so in the old API docs, not sure about new ones). You can use the geocode search operator in the query, though... Try this for new york: geocode:40.714550,-74.007124,15mi -Chad On Wed, May 27, 2009 at 4:35 PM, Jonas