3 ms·

I don't think your question really makes sense. The request to load the embedded YouTube video will contain the same Do Not Track headers as the requests loadin

I don't think your question really makes sense. The request to load the embedded YouTube video will contain the same Do Not Track headers as the requests loading your own site. It is up to the site owner to respect them (in this case YouTube). It's not your responsibility to try to re-host content from other sources in order to comply with the DNT request.

r3bl 9y ago
If I really want to enforce a DNT policy on my website, it is absolutely my responsibility to find a way to not embed a YouTube video by default, since I do know that YouTube doesn't give a crap about a DNT policy. It is also in my responsibility to not include original social sharing buttons, since they break DNT. It should also be my responsibility to add an option to break DNT upon user's desire (for example, click-to-enable YouTube embed and click-to-enable sharing buttons), and, if we take things to extreme, I should even be able to have a small icon next to every single link that will tell the users if the website I linked to respects DNT or not. The DNT thing is broken completely for the end users, there's no point in arguing about that. But, if I, as the website owner, want to respect it for my viewers, I need some strategy on how to do so, which is exactly what this question is about. I firmly believe that: 1. Enabling DNT by default is a bad idea, but the option should be there. 2. If my visitor enables DNT on his own browser, and that decision was solely made by the visitor (as in, not enabled by default which IE tried to do some time ago), I should at least try respecting it as much as possible. This Ask HN is specifically posted to see how can I accomplish #2.
- STRML 9y ago
  I agree that the IE decision was practically braindead and killed the utility of DNT. Because of it, we have no idea if the user actually specifically wants DNT (and this may degrade the user experience, so it should be opt-in), or their browser vendor simply decided for them.

r3bl 9y ago

If I really want to enforce a DNT policy on my website, it is absolutely my responsibility to find a way to not embed a YouTube video by default, since I do know that YouTube doesn't give a crap about a DNT policy. It is also in my responsibility to not include original social sharing buttons, since they break DNT. It should also be my responsibility to add an option to break DNT upon user's desire (for example, click-to-enable YouTube embed and click-to-enable sharing buttons), and, if we take things to extreme, I should even be able to have a small icon next to every single link that will tell the users if the website I linked to respects DNT or not. The DNT thing is broken completely for the end users, there's no point in arguing about that. But, if I, as the website owner, want to respect it for my viewers, I need some strategy on how to do so, which is exactly what this question is about. I firmly believe that: 1. Enabling DNT by default is a bad idea, but the option should be there. 2. If my visitor enables DNT on his own browser, and that decision was solely made by the visitor (as in, not enabled by default which IE tried to do some time ago), I should at least try respecting it as much as possible. This Ask HN is specifically posted to see how can I accomplish #2.

STRML 9y ago
I agree that the IE decision was practically braindead and killed the utility of DNT. Because of it, we have no idea if the user actually specifically wants DNT (and this may degrade the user experience, so it should be opt-in), or their browser vendor simply decided for them.