mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-10 00:12:09 +00:00
Remove superfluous sentence
This commit is contained in:
parent
d868be3da0
commit
28f70689a4
2 changed files with 0 additions and 4 deletions
|
@ -67,8 +67,6 @@ To be extra safe, you can whitelist exactly what scripts can run with a Content
|
|||
|
||||
If you're concerned about Google breaking the spec and opting you in even after you've not done so yourself, what reason do you have to believe that they'll stop there? There's nothing preventing Google from ignoring your `Permissions-Policy` header, either.
|
||||
|
||||
Don't tack a new header onto every request because someone read a post by someone else who read part of a GitHub README.
|
||||
|
||||
## Take a breath
|
||||
|
||||
Please, don't spam maintainers of web server/backend software to tell them to include this header by default when it may or may not actually reduce user fingerprints. Don't tell webmasters that they have a *moral obligation* to add a Permissions Policy header either.² You don't need to add this permission policy to every request, just as you don't need to wear a helmet for every form of physical activity.
|
||||
|
|
|
@ -61,8 +61,6 @@ To be extra safe, you can whitelist exactly what scripts can run with a [Content
|
|||
|
||||
If you're concerned about Google breaking the spec and opting you in even after you've not done so yourself, what reason do you have to believe that they'll stop there? There's nothing preventing Google from ignoring your `Permissions-Policy` header, either.
|
||||
|
||||
Don't tack a new header onto every request because someone read a post by someone else who read part of a GitHub README.
|
||||
|
||||
Take a breath
|
||||
-------------
|
||||
|
||||
|
|
Loading…
Reference in a new issue