I've been using the UserStreams API for quite some time using the
Phirehose patches.  We are trying to get SiteStreams to work and made
the necessary modifications to the UserStreams code to work with
SiteStreams.  Unfortunately, I am always receiving this error when I
try to connect and get data from the stream:

HTTP ERROR 400: Bad Request (45Must specify some followings to use
sitestreams, e.g. follow=1,2,3,4)

The following is output for how I'm trying to connect and what I'm

+ Connecting to twitter stream: https://sitestream.twitter.com/2b/site.json
with params: array (  'delimited' => 'length',  'replies' => 'all',
'with' => 'user',  'follow' => '17448575',)
+ Resolved host sitestream.twitter.com to
+ Connecting to
+ Connection established to
    [oauth_consumer_key] => [Surpressed]
    [oauth_nonce] => 17c00ae9913dd68d5d9c493c1474807c
    [oauth_signature_method] => HMAC-SHA1
    [oauth_timestamp] => 1311277876
    [oauth_token] => [Surpressed]
    [oauth_version] => 1.0
string(307) "POST&https%3A%2F%2Fsitestream.twitter.com%2F2b
+ POST /2b/site.json HTTP/1.1
+ Host: sitestream.twitter.com:443
+ Authorization: OAuth realm="https://sitestream.twitter.com/2b/
site.json", oauth_consumer_key="[Surpressed]",
oauth_timestamp="1311277876", oauth_signature_method="HMAC-SHA1",
oauth_version="1.0", oauth_signature="%2FKI0z4%2BMKXZVPQig0tt3YMMtBEk
+ delimited=length&replies=all&with=user&follow=17448575
+ HTTP failure 1 of 20 connecting to stream: HTTP ERROR 400: Bad
Request (45Must specify some followings to use sitestreams, e.g.
follow=1,2,3,4). Sleeping for 10 seconds.

I was wondering if anyone had any ideas as to why we would receive
this message.  Any help would be greatly appreciated, we're struggling
with this issue.


Have you visited the Developer Discussions feature on 
https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings: 

Reply via email to