Wrote a patch to make it significantly easier to test whether a request or response contains certain headers in http-types. Similarish ergonomics as Ruby's net::http (: https://github.com/http-rs/http-types/pull/110 …pic.twitter.com/VXlNOZuBzf
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, you're not missing anything tho -- that's all it is (not counting fancy headers such as cookies and mime types). We try hard throughout our docs to explain that both Request and Response are nothing but headers + streaming body + either URL+Method or StatusCode. This fits.
Nah, I mean sure. But then I use `res[“content-type”]` but `res.body()` and `res.status()`? To me that feels icky, I don’t know (but maybe I also need to see that API in full use)
Oh yeah we don't expose res.body either -- Request and Response implement AsyncRead / AsyncWrite directly. Much like Node.js provides a stream API on http req/res.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.