preload nodes are blocked by Privacy Badger
vmx opened this issue · comments
I have the Privacy Badger extension installed in my Firefox.
I was browsing https://vitriol.co/QmccRaHCrUKZwZpjdJFiTTdgp8FG3ALFDZQexaYgit3NCF/QmYJvZjnw8c1DqFbW1BpWmvb3jVg8fQYRUs6UzzEyosagA and it didn't load. The reason is that Privacy Badger decided to block content from node0.preload.ipfs.io and node1.preload.ipfs.io.
I don't know if we can do anything about it, I just wanted to bring it up.
per their FAQ:
Domains will only be blocked or screened if the Privacy Badger code inside your browser actually observes the domain collecting unique identifiers after it was sent a Do Not Track message.
Weird.
To get unblocked, we can post (and commit to following, of course) a policy text document to a specific URL (eg. https://node*.preload.ipfs.io/.well-known/dnt-policy.txt)
@mburns sounds like a very good idea.
Issues caused by Privacy Badger are raised quite often and people burn a lot of time debugging why images do not load (e.g. https://github.com/filecoin-project/website/issues/46) :)
We should set up that file for our public gateways
at ipfs.io, dweb.link and *.ipfs.dweb.link as well.
This appears to no longer be the case, as I can't reproduce the issue.
That said, having a state policy isn't a bad idea. @olizilla thoughts on the EFF's Do Not Track pledge? https://www.eff.org/.well-known/dnt-policy.txt