Live data from Hacker News

Why HTTP/2.0 does not seem interesting (2012)

varnish-cache.org

41–50 of 50 posts

Re: Why HTTP/2.0 does not seem interesting (2012)

#41
post #8

Earlier quoted context omitted.

Oh yes, the regulation was rushed in by people not really sure what to do or what was happening. Why it couldn't be a browser option, I have no idea.

Isn't it already a browser option?

Yes. But the default browser options are "accept all cookies, without asking", which goes against the spirit of the law, and also the letter.

Re: Why HTTP/2.0 does not seem interesting (2012)

#42
post #40

Earlier quoted context omitted.

Please correct me if I'm wrong, but wasn't that the UK's law? If it was, they seemed to backtrack on it and say that it's fine as long as you mention it in your site's TOS

It was an EU wide law. Each country implemented EU in similar but different ways.

Thanks for that!

Re: Why HTTP/2.0 does not seem interesting (2012)

#43
post #40

Earlier quoted context omitted.

Please correct me if I'm wrong, but wasn't that the UK's law? If it was, they seemed to backtrack on it and say that it's fine as long as you mention it in your site's TOS

It was an EU wide law. Each country implemented EU in similar but different ways.

It is a EU Directive: https://en.wikipedia.org/wiki/Directive_(European_Union)

AFAIK the EU dictates the result, not the means. UK's first implementation of the e-Privacy Directive was unfortunate, but I don't think it means the directive was a bad idea.

Re: Why HTTP/2.0 does not seem interesting (2012)

#44
post #33
post #31

Earlier quoted context omitted.

"For advertisers this is a non-starter, because it prevents you from knowing the size of your audience. All sites would immediately begin requiring some form of "login" in your scenario in order to enable tracking again." If this is really a non-starter for advertisers, then mandating it will effectively ban advertising, non? Remember: your business model is not sacrosanct! Disruption!

It will also kill most "free content" websites that live off the ads revenue. Are you ready for paywalls everywhere, even if subscription is 25 � / mo?

Your symbol comes out as a Unicode replacement character for me. What was it supposed to be?

Re: Why HTTP/2.0 does not seem interesting (2012)

#45
post #43
post #40

Earlier quoted context omitted.

It was an EU wide law. Each country implemented EU in similar but different ways.

It is a EU Directive: https://en.wikipedia.org/wiki/Directive_(European_Union) AFAIK the EU dictates the result, not the means. UK's first implementation of the e-Privacy Directive was unfortunate, but I don't think it means the directive was a bad idea.

An "EU Directive" is a law, it's decided on in the same democratic manner that (say) UK laws are decided on. It's like how in the UK there are "Acts of Parliament" (i.e. laws).

It's up to individual countries to implement the minimum, and likewise, each country will implement each one slightly different. The UK law and the EU Directive are basically the same, "It's illegal to do X, Y and Z unless you do W etc." There isn't really a mean/results differnce here.

Re: Why HTTP/2.0 does not seem interesting (2012)

#46
post #44
post #33

Earlier quoted context omitted.

It will also kill most "free content" websites that live off the ads revenue. Are you ready for paywalls everywhere, even if subscription is 25 � / mo?

Your symbol comes out as a Unicode replacement character for me. What was it supposed to be?

It was the cent symbol, ¢; somehow it was broken in transmission.

Re: Why HTTP/2.0 does not seem interesting (2012)

#47
post #31
post #26

Earlier quoted context omitted.

For advertisers this is a non-starter, because it prevents you from knowing the size of your audience. All sites would immediately begin requiring some form of "login" in your scenario in order to enable tracking again. If you can't track uniques, you can't sell ads, and that's pretty much all there is to it. So there's huge incentive to undermine any scheme to prevent unique user tracking. The solution is to somehow…

"For advertisers this is a non-starter, because it prevents you from knowing the size of your audience. All sites would immediately begin requiring some form of "login" in your scenario in order to enable tracking again." If this is really a non-starter for advertisers, then mandating it will effectively ban advertising, non? Remember: your business model is not sacrosanct! Disruption!

I'm not arguing against banning advertising. Actually, I think that would be a fine idea.

Just recognize that unless you do ban advertising, the result of this change will not be what's intended. The intended result is that websites, in general, stop tracking anonymous users. Instead, it will result in every user being explicitly tracked.

The most important issue here is that the political feasibility of reducing tracking of anonymous users is equivalent to the political feasibility of banning advertising.

(I'm slightly overselling here -- in reality, a good amount of advertising of the "sponsorship" form would still work. But the impact would be large enough that most websites would force login as I describe rather than stop tracking people.)

Re: Why HTTP/2.0 does not seem interesting (2012)

#48
post #26

Earlier quoted context omitted.

For advertisers this is a non-starter, because it prevents you from knowing the size of your audience. All sites would immediately begin requiring some form of "login" in your scenario in order to enable tracking again. If you can't track uniques, you can't sell ads, and that's pretty much all there is to it. So there's huge incentive to undermine any scheme to prevent unique user tracking. The solution is to somehow…

To sell ads you don't need to show exact size of audience, estimation is enough as proven by TV.

That's a very good point. This would definitely happen to some degree. But it would still hurt internet advertising a good deal not to be able to track uniques, to show you an ad only once per day, to count how many people have been shown an ad, etc. even if you could know about how many people were on the site.

The result would likely be tracking via login as I describe, rather than true anonymity.

Re: Why HTTP/2.0 does not seem interesting (2012)

#49
post #21

Earlier quoted context omitted.

And in theory less data, right? a session ID doesn't need to store the kilobytes that cookies do.

Why can't there be multiple sessions for different functionalities? I am not sure people are going to relinquish the cookie concept. All the sessions are doing is have the "cookies" transported as part of the HTTP message and not as a separate file (payload)

Cookies are sent in the Cookie and Set-Cookie headers. No separate files.

Re: Why HTTP/2.0 does not seem interesting (2012)

#50
post #46
post #44

Earlier quoted context omitted.

Your symbol comes out as a Unicode replacement character for me. What was it supposed to be?

It was the cent symbol, ¢; somehow it was broken in transmission.

That time it worked. Not sure why it broke the first time.
Post reply on HN