Firehose Access

[Josh Perry]

Who do we need to talk to about accessing the firehose API? We would
only need a filtered feed as long as the filter is realtime updateable.

[Mateusz Berezecki]

On Sun, Mar 8, 2009 at 1:11 AM, Josh Perry <jo...@6bit.com> wrote:
>
> Who do we need to talk to about accessing the firehose API?  We would
> only need a filtered feed as long as the filter is realtime updateable.
>

I'd second that question. On what conditions is firehose access
granted to 3rd parties?

Mateusz

[Doug Williams]

Have you seen the following?

http://apiwiki.twitter.com/FAQ#Whenwillthefirehosebeready

Doug
@dougw

--
Doug Williams

do...@igudo.com
http://www.igudo.com

[Sylvain Munaut]

On Mar 8, 7:13 pm, Doug Williams <do...@igudo.com> wrote:
> Have you seen the following?
>
> http://apiwiki.twitter.com/FAQ#Whenwillthefirehosebeready

Yes and somehow the "By late January, early February 2009" makes it
sound like this FAQ entry is outdated ...
Might be worth to s/2009/2010/g :)

Sylvain

[Doug Williams]

Sylvain,
I've updated the FAQ to reflect the deadline slippage:

We thought the "firehose" (the near-realtime stream of all public
status updates on Twitter) would be shipped by February 2009, but the
deadline has slipped a bit. We've pushed back our timeline for testing
with a small group of trusted partners to Q2 2009...

Thank you for your patience,
Doug Williams
Twitter API Support
http://twitter.com/dougw

[Ken Sheppardson]

I'm just reading http://apiwiki.twitter.com/Streaming-API-Documentation#firehose

So is the firehose live?

I see that this is "available only to approved parties, and requires a
signed agreement to access."

Are the approval guidelines/criteria and text of the agreement
available for review?

-Ken

On Mar 10, 3:56 pm, Doug Williams <d...@twitter.com> wrote:
> Sylvain,
> I've updated the FAQ to reflect the deadline slippage:
>
> We thought the "firehose" (the near-realtime stream of all public
> status updates on Twitter) would be shipped by February 2009, but the
> deadline has slipped a bit. We've pushed back our timeline for testing
> with a small group of trusted partners to Q2 2009...
>
> Thank you for your patience,
> Doug Williams

> Twitter API Supporthttp://twitter.com/dougw

[Doug Williams]

We currently have all of the partners we need for testing. The section of text applicable to our post-testing process is pasted from the FAQ [1] below.

Once we're confident in the stability of the service, we'll add partners on a case-by-case basis. We may allow a wider selection of clients to consume subsets of the public stream (that is, updates from a collection of user IDs or matching specific search terms). We do not intend to allow anonymous, unregulated public access to this stream for any number of legal, financial, and technical reasons.

We do not intend to share the TOS used by test partners at this time.

1. http://apiwiki.twitter.com/FAQ#Whenwillthefirehosebeready

Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw