The work to do this isn't free. YouTube already has their code working, but they don't expect browsers to be blocking arbitrary requests or injecting their own javascript into the page. These kind of breakage are not free for YouTube to fix and often YouTube is the one taking the reputational hit for their site being broken. It ultimately is antisocial behavior to be breaking other's sites even if technically they can workaround the bugs being added.

▲

lcnPylGDnU4H9OF 5 days ago | parent [-]

> antisocial behavior

This is hard to take seriously in defense of YouTube. I suppose the most respectful answer is that I'll be willing to stop when they do.

▲

humpty-d 5 days ago | parent [-]

Stop what? Showing ads? They have to fund it somehow, there will always be ads. Most users aren't willing to pay for anything on the internet, and unfortunately revenue is required to run anything at scale. You can charge users, show ads, or maybe get funding from Saudis.

▲

kentm 5 days ago | parent | next [-]

> Stop what? Showing ads?

Using abusive advertising practices and being reasonable about the number of ads shown.

▲

lcnPylGDnU4H9OF 5 days ago | parent | prev [-]

> Stop what?

Tracking with javascript.

▲

humpty-d 5 days ago | parent [-]

So just track you on the back end instead? I don't know what that really changes. If you mean to say just not track you at all and show you untargeted ads, well they are worth less, so they'll have to blast you with more of them.

▲

lcnPylGDnU4H9OF 5 days ago | parent [-]

> I don't know what that really changes.

It changes what they assume to do with my hardware and user agent.

▲

humpty-d 5 days ago | parent [-]

Why be cryptic and weird when you can just plainly say whatever it is that you actually mean? Communicate clearly, nobody knows what the f you're on about.

	▲	lcnPylGDnU4H9OF 5 days ago \| parent [-]
		> cryptic and weird Mine is a common opinion within this community. I won't deny that I was short in my replies but it is hard to know what is over-explaining in this context. Additionally, it seems that "tracking with javascript" is pretty much exactly the topic of these comments so I'm not sure why I should not have assumed that it would be clear what I meant, especially when my first comment was explicitly about YouTube tracking on the back end.