You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we're on twitter, we need to rethink how often we make calls to twitter lest we get blocked on apis.
One solution is to have a process that gets all tweets for every game and imports them appropriately. I'm not a fan of this since this potentially involves building another process that costs money (although I suppose it could run on the existing separate worker).
Another solution is to do is to implement a counter on the twitter for a game so that users can't just slam the button a billion times a second.
Now that we're on twitter, we need to rethink how often we make calls to twitter lest we get blocked on apis.
One solution is to have a process that gets all tweets for every game and imports them appropriately. I'm not a fan of this since this potentially involves building another process that costs money (although I suppose it could run on the existing separate worker).
Another solution is to do is to implement a counter on the twitter for a game so that users can't just slam the button a billion times a second.
The limit information from twitter is here: https://dev.twitter.com/rest/public/rate-limiting
The text was updated successfully, but these errors were encountered: