News for hackers. Stuff that matters.
Re:Last Call: HTTP2 by jacquesm on Thursday January 01, 2015 @08:24PM (#8825102)
Google doesn't need a way to track you using SPDY, they are present on just about every page already, assuming they don't serve it outright and that you didn't navigate there using their search engine.
Re:Last Call: HTTP2 by bsdetector on Thursday January 01, 2015 @08:45PM (#8825145)
That's interesting, because I block analytics and some other Google domains and I use Bing.

Why push SSL so hard for sites many of which are just public info anyway? Because then you can't really use proxies so almost always 1 connection is 1 person.

The HTTP connection timeout is like 15 seconds or less in popular software. One of the justifications for SPDY/HTTP2 is that with one connection it can be kept open for many minutes or even hours without using too many resources.

Instead of many separate, possibly proxied connections to doubleclick you have one connection that lasts maybe even a whole browsing session. Google may not need this, but it's certainly better for them.

Re:Last Call: HTTP2 by hrjet on Friday January 02, 2015 @12:14AM (#8825630)
That's an interesting thought. Have created an [issue in our browser](https://github.com/UprootLabs/gngr/issues/54) to investigate our implementation further.