Hey there, The technical architecture we're currently using to host this file doesn't support serving gzipped content in the standard manner (using the HTTP Accept-Encoding header). Because we can't be sure gzip is supported by the user agent making the request (especially with proxies) we prefer to serve the file uncompressed, prioritizing compatibility over performance.
Thanks for your feedback! That's something we're looking to improve in the future. Arnaud / @rno <http://twitter.com/rno> On Fri, May 20, 2011 at 9:49 AM, cfalar <[email protected]> wrote: > Hi, > its can be a 20k save on a 30k initial file. > i try with Firefox 4 with Accept-Encoding gzip,deflate > > I work for a tv company and we have the twitter widget on many page. > We have a lot of external javascript so a 20k saving is good. > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
