I'm playing with the oauth2 support in v2-beta with an http client that doesn't support gzip decoding. (My client is http spec compliant but can't deal with the non-compliance of the api on this issue). Am I out of luck?
Starting in V2, the API will honor deflate Accept-Encodings (it still defaults to GZIP in the absence of an Accept-Encoding). So, if deflate is an option then you've got a work around.
I'm curious as to what client you're using that doesn't support GZIP? That's kind of egregious in 2011.