I believe I answered this question on Nov 12 (message 2) in this
thread.
Thanks John,
I am not sure I understand when you say There is no single role in
the Streaming API that will allow that many follows and track
parameters., your documentation says :
The default access level allows up to 200 track keywords and 400
follow userids. Increased access levels allow
Thanks a lot John for this clear explaination.
Is it possible to have the following settings:
- superfeedr_foll as Shadow
- superfeedr_trac as TrackRestricted
That would truly be awesome. I will change our implementation so that
we use 2 different accounts for the 2 purposes.
Again, thx.
Julien
Please request the additional access by whatever means you requested
your initial access.
-John
On Nov 15, 3:35 pm, Julien julien.genest...@gmail.com wrote:
Thanks a lot John for this clear explaination.
Is it possible to have the following settings:
- superfeedr_foll as Shadow
-
Ok I sent an email, but Ryan takes forever to respond to my emails :/
Isn't there anything you could do?
thanks,
On Nov 15, 6:34 pm, John Kalucki jkalu...@gmail.com wrote:
Please request the additional access by whatever means you requested
your initial access.
-John
On Nov 15, 3:35 pm,
John, Cameron... Any clue?
On Nov 12, 11:05 am, Julien julien.genest...@gmail.com wrote:
Indeed... sorry about that!
On Nov 12, 10:52 am, Cameron Kaiser spec...@floodgap.com wrote:
For some reason, my previous post didn't show up :/
That's because you're a new poster and the
Thanks John, I'll review all that and we'll post more info soon.
Thanks for listening!
On Nov 12, 6:39 am, John Kalucki jkalu...@gmail.com wrote:
413 usually means too long on the Streaming API. Too many
predicates, or perhaps a URL of crazy length. This is documented in
the wiki.
First,
For some reason, my previous post didn't show up :/
So, we don't get the error when we stay in the limitations of the
default access level (200 track and 400 userids).
If we go beyond that, we get : HTTP/1.1 413 Request Entity Too Large
Could it be that our username hasn't been approved despite
John,
This is exactly what we post to your servers (I just hid the
Authorization) :
POST /1/statuses/filter.json HTTP/1.1
Host: stream.twitter.com
User-agent: TwitterStream
Authorization: Basic X==
Content-type: application/x-www-form-urlencoded
Content-length: 13609
Indeed... sorry about that!
On Nov 12, 10:52 am, Cameron Kaiser spec...@floodgap.com wrote:
For some reason, my previous post didn't show up :/
That's because you're a new poster and the volunteer mods have to approve
them first. Give us a chance :)
--
10 matches
Mail list logo
