Hey @TwitterAPI (or API users),
IIRC there was a one IP per APP limit for streaming endpoints. I can't seem to find that in the docs anymore though. Has that changed? I want to be as compliant as possible.
Does that apply to statuses/sample, too? As in can I have one statuses/sample connection and one statuses/filter on the same IP, or is it one or the other?
-
-
I’m not certain, since you ask, and given sample is (by design) random data, I’m not sure why you’d implement something to listen to both concurrently? I’d also point out that both are in the process of being replaced. Filter is already in testinghttps://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888 …
-
I'm working on anti-abuse software. Filter is useful because there are typically high (albeit dynamic) abuse keywords, so it's easy to identify. *But* sample allows me to have less obviously biased coverage. But thanks, I'll develop on the new ednpoint!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.