Skip to content
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

Clarify, whether the policies should be posted word-by-word #23

Open
Boldewyn opened this issue Dec 2, 2015 · 3 comments
Open

Clarify, whether the policies should be posted word-by-word #23

Boldewyn opened this issue Dec 2, 2015 · 3 comments

Comments

@Boldewyn
Copy link

Boldewyn commented Dec 2, 2015

This is a request for documentation. https://www.eff.org/dnt-policy says to include the policy verbatim under .well-known/dnt-policy.txt. Also, this repo contains a JSON file with hashes for the respective versions.

However, the text of the policy contains the sentence

This file will always be posted via HTTPS at https://example-domain.com/.well-known/dnt-policy.txt
to indicate this fact.

On reading the policy, it seems, that this sentence should be updated to contain the actual domain that issues the policy. In fact, that's how I did it on codepoints.net: https://codepoints.net/.well-known/dnt-policy.txt

Of course, any hashes will be different then. But apart from the above mentioned "verbatim" I found no note, if the file is indeed meant to be included just as downloaded from Github, or is a template (as https://example-domain.com/ suggests), that needs editing.

The intended way of embedding should be published at the FAQ at https://www.eff.org/dnt-policy, too.

@baloo
Copy link

baloo commented Jun 29, 2016

I'm facing the same issue, the eff.org itself posted it verbatim (see https://www.eff.org/.well-known/dnt-policy.txt) so I tend to think it should be verbatim. I'd go this way for now.

@cooperq
Copy link

cooperq commented Jul 6, 2016

@baloo is right, the text should be included verbatim. The domain should not be changed to your own domain but left as example-domain.com

@Boldewyn
Copy link
Author

Boldewyn commented Jul 7, 2016

Yes, I deduced that from various clues. This issue is more meant as a documentation bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants