I've noticed that when creating a Filtered Stream and following a large amount of users (over 1000 or so in my case), that I start consistently receiving 503 responses from stream.twitter.com. Twitter supports up to 5000, so I don't think I'm hitting a limit there. If I reduce the number of followed users, the connection is established successfully. I believe the issue is related to the extraordinarly long URL that TweetInvi creates when establishing the connection, by including all of the followed IDs in the "follow" querystring parameter.
Would you please consider providing the option of including track, follow, etc... parameters in the posted data rather than the URL? Twitter recommends this rather than using an extremely long URL.
Their comments on this are visible here:
[https://dev.twitter.com/docs/api/1.1/post/statuses/filter](https://dev.twitter.com/docs/api/1.1/post/statuses/filter)
In the meantime, I'm going to have to roll-my-own client in order to meet some project deadlines, but I'd LOVE to be able to switch back to TweetInvi as soon as this capability is there.
Comments: ** Comment from web user: linvi **
Would you please consider providing the option of including track, follow, etc... parameters in the posted data rather than the URL? Twitter recommends this rather than using an extremely long URL.
Their comments on this are visible here:
[https://dev.twitter.com/docs/api/1.1/post/statuses/filter](https://dev.twitter.com/docs/api/1.1/post/statuses/filter)
In the meantime, I'm going to have to roll-my-own client in order to meet some project deadlines, but I'd LOVE to be able to switch back to TweetInvi as soon as this capability is there.
Comments: ** Comment from web user: linvi **
Test if this is now working with HttpClient.