Thanks for the clarification, the firehose will still probably be the best solution for us, it's just good to know we'll need to do some filtering of it on our end.
On Dec 6, 2:51 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > No, the firehose is distinct from Twitter Search. It's simply for > delivering the entire stream of public updates. We may add filters > and such in the future, but for now, we're just focusing on this one > need that our partners have. > > > > On Sat, Dec 6, 2008 at 11:42, drupalot <[EMAIL PROTECTED]> wrote: > > > Sounds good. Thanks Alex. > > > Btw, will the firehose have the same capacity to filter before pulling > > (or received the push) as regular feeds do (via advanced search or > > elements in the feed URL directly)? > > > On Dec 6, 2:37 am, "Alex Payne" <[EMAIL PROTECTED]> wrote: > >> The firehose will provide all the fields returned in the REST API. Our > >> Atom feed is limited to those attributes that fit an Atom entry; use > >> XML or JSON for all attributes. > > >> On Fri, Dec 5, 2008 at 12:37, drupalot <[EMAIL PROTECTED]> wrote: > > >> > Looks like I can pull username, tweet (text and URL) and timestamp > >> > from the public timeline (or advanced search slice of the public > >> > timeline) atom feed. Can I also pull image, reply-to URL, and > >> > location? If not, will the upcoming firehose provide these additional > >> > fields by any chance, or is there another aspect of the search API I > >> > could utilize for this? Thanks for any help on this front. > > >> -- > >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
