Consuming rate-limited APIs at scale is like interacting with a database that has pretty painful latency. I keep "inventing" what are surely preexisting design patterns / solutions to this problem. Can anyone point me to a good guide so that I can stop wasting my time?
-
-
let me know when you find it...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.