You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So I still have a *ton* of work to do, and this code is not particularly well optimized (or complete), but my naive PoC for this is showing nearly a 2x speedup for Active Record. (measuring `Post.all.each(&:attributes)` on 1k records)
A naive implementation with a 200% speed up? Imagine if you actually optimized it.
I think the answer is actually 2x. I spent a bit of time optimizing this morning before I scrapped the prototype. Instruments shows all the overhead on the Ruby side
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
