-
-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support YouTube "privacy-enhanced mode" (youtube-nocookie.com) #82
Comments
This would require adding this domain to the manifest permissions as well.
This comment is for my future reference or someone implementing it.
…On Tue, Aug 6, 2019, 1:23 PM Anton Bershanskiy, ***@***.***> wrote:
Summary
This extension already supports URLs like https://www.youtube.com/embed/*
used for embedding YouTube in iframes on other pages, so I think it should
also support URLs like https://www.youtube-nocookie.com/embed/* used for
embedding videos in YouTube "privacy-enhanced mode".
Details
From official Google documentation
<https://support.google.com/youtube/answer/171780> (under "Turn on
privacy-enhanced mode" dropdown):
Privacy Enhanced Mode allows you to embed YouTube videos without using
cookies that track viewing behavior.
...
To use Privacy Enhanced Mode, change the domain for the embed URL in your
HTML from https://www.youtube.com to https://www.youtube-nocookie.com...
youtube-nocookie.com is an official YouTube domain that serves videos for
iframes without setting cookies. Some site administrators prefer these URLs
over regular ones for simplifying compliance with EU regulations (e.g.,
cookie directive or GDPR). Some users install browser extensions or scripts
that automatically switch the URL for a slight improvement in privacy
(reducing behavioral tracking, but not the number of ads).
I believe it would be nice if this extension supported this mode as well,
however, this feature might need to be optional because if users do not
want to be tracked by YouTube, they might not want to be tracked by this
extension. Note that it's already possible in modern Chrome/Chromium
versions (user can individually disable sites under extension's
permissions). Something similar should eventually land in Firefox.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=ADAZV4DESJTV6SXJSMPAVQDQDGXRJA5CNFSM4IJYSIY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HDWDPNQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADAZV4C3BUWX2FZUJU5HAZ3QDGXRJANCNFSM4IJYSIYQ>
.
|
@ajayyy I did :D should be the same as the "normal" domain |
Maybe some parts can be disabled on this domain? |
Well I think its the same as http://www.youtube.com/embed |
I am referring to:
|
@ajayyy Ultimately, there are two approaches: make access to |
Summary
This extension already supports URLs like
https://www.youtube.com/embed/*
used for embedding YouTube in iframes on other pages, so I think it should also support URLs likehttps://www.youtube-nocookie.com/embed/*
used for embedding videos in YouTube "privacy-enhanced mode".Details
From official Google documentation (under "Turn on privacy-enhanced mode" dropdown):
youtube-nocookie.com
is an official YouTube domain that serves videos for iframes without setting cookies. Some site administrators prefer these URLs over regular ones for simplifying compliance with EU regulations (e.g., cookie directive or GDPR). Some users install browser extensions or scripts that automatically switch the URL for a slight improvement in privacy (reducing behavioral tracking, but not the number of ads).I believe it would be nice if this extension supported this mode as well, however, this feature might need to be optional because if users do not want to be tracked by YouTube, they might not want to be tracked by this extension. Note that it's already possible in modern Chrome/Chromium versions (user can individually disable sites under extension's permissions). Something similar should eventually land in Firefox.
The text was updated successfully, but these errors were encountered: