fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-24 05:02:10 +00:00
Code Issues Projects Releases Wiki Activity

Remove superfluous sentence

Browse source
This commit is contained in:
Rohan Kumar 2021-04-16 21:25:30 -07:00
parent d868be3da0
commit 28f70689a4
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
2 changed files with 0 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/posts/permissions-policy-floc-misinfo.gmi
View file

@ -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. 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 ## 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. 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.

2
content/posts/permissions-policy-floc-misinfo.md
View file

@ -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. 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 Take a breath
------------- -------------