Twitter速率限制IP / OAuth关注(Twitter Rate Limiting IP/OAuth Concerns)

Twitter速率限制IP / OAuth关注(Twitter Rate Limiting IP/OAuth Concerns)

我有一系列的webapps，使用Public Streaming API收集与主题相关的所有术语。 到目前为止，我一直在为每个流创建一个新帐户，在该帐户上设置一个新的Twitter应用程序，复制OAuth令牌，启动一个新的EC2实例，以及设置流，这是一个非常非常艰巨的路线。

这允许我使用来自多个不同IP的流，在创建应用时使用生成器工具轻松生成OAuth，并且因为它们各自在不同的帐户中，所以我不满足任何帐户限制。

我想知道我能做些什么来加快这个过程，特别是在EC2实例方面。 我可以使用不同的帐户在同一个实例上运行一堆流吗？

I have a series of webapps that collects all terms relating to a subject using the Public Streaming API. So far, I've been taking a very, very arduous route of creating a new account for each stream, setting up a new Twitter application on that account, copying the OAuth tokens, spinning up a new EC2 instance, and setting up the stream.

This allows me to have the streams coming from multiple different IPs, OAuth generation is easy with the generator tool when you create an app, and because they are each in different accounts I don't meet any account limits.

I'm wondering if there's anything I can do to speed up the process, specifically in terms of EC2 instances. Can I have a bunch of streams running off the same instance using different accounts?

最满意答案

如果您从一台机器运行多个消费者，您可能会被暂时禁止，反复禁止可能最终会让您被禁止更长时间。 至少，这在过去几次发生在我身上。

我当时发现的是：

相同的凭据，相同的IP - >阻止/禁止 不同的凭据，相同的IP - >大多数都可以，但不时被禁止 不同的凭据，不同的IP - >好的

这是几年前的事情，所以我不确定这是否仍然如此，但我希望twitter能够收紧规则，而不是放松它们。

（另外，我认为你侵犯了他们的ToS）

If you run multiple consumers from a single machine you may be temporarily banned, repeated bans may end up getting you banned for longer periods. At least, this happened to me a few times in the past.

What I had found at the time was:

same credentials, same ip -> block/ban different credentials, same ip -> mostly ok, but banned from time to time different credentials, different ip -> ok

This was a few years ago, so I am not sure the same is still true, but I'd expect twitter to have tightened the rules, rather than having relaxed them.

(Also, I think you're infringing their ToS)