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
Heh, found out today that Rust's async model is turning out to be pretty close to how Node works. This example spawns up 4 event loops, and round-robins requests between them. Like with require('cluster')! https://github.com/tokio-rs/tokio-core/blob/master/examples/echo-threads.rs …
My hope is that this might be done more neatly in the future. It'd be cool if it became closer to Golang's threading model. Golang doesn't make use of round-robin to assign work. Instead it knows what the load of each core is and schedules tasks accordingly.
Also: a lot of complexity here seems to come from working around OS shortcomings. What if operating systems had a light threading abstraction built in? Would that make sense even? There seem to be many people working on this problem in parallel. So maybe?
Tldr: I'm impressed by Go's threading model, and wish Rust could schedule work in the same way 
They way I see it node and golang are specialists here, they were built for this. In case of rust is more like 'we now get to do async io' too
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
