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
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
The only easy win I see left is if Ruby had an equivalent of `HashMap::with_capacity` (or `rb_ary_new_capa` on their end), as ~3% of time is spend re-allocating a hashmap with a known size
Though this is also in the benchmark for `ActiveRecord::Base#attributes` which literally nobody calls, but is a good proxy for "I read all of the fields on this thing"
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
