Add media assets to IPFS

[jonaharagon]

Description

Testing

Related: #1373

Check List

• [x] I have read and understand the contributing guidelines.

[netlify[bot]]

Deploy preview for privacytools-io ready!

Built with commit f0965719ee355da55fa40c1642898929040ccd75

https://deploy-preview-1374--privacytools-io.netlify.com

[jonaharagon]

Hmm. At a glance, having a CSP might be fundamentally incompatible with how IPFS operates which might make this change impossible.

---

<meta http-equiv="Content-Security-Policy" content="default-src 'none'; script-src 'self' 'unsafe-inline' https://*.privacytools.io 127.0.0.1; style-src 'self' 'unsafe-inline' 127.0.0.1; img-src 'self' data: https://*.privacytools.io 127.0.0.1; object-src 'none'; frame-src https://stats.privacytools.io; font-src 'self'; manifest-src 'self';">

[Mikaela]

I wonder if the IPFS gateway should be a variable in _config.yml like I do with mikaela.info ?

[jonaharagon]

I don't see why we'd ever change it though. I wouldn't want to trust a third-party gateway for non-IPFS users (especially since most traffic would be going to whatever gateway we specify).

Obviously if this were merged the IPFS gateway we host would get a little more attention than it currently does :P

[Mikaela]

I don't see why we'd ever change it though. I wouldn't want to trust a third-party gateway for non-IPFS users (especially since most traffic would be going to whatever gateway we specify).

What if the gateway ever gets renamed or there will be IPFS gateway redirector instead or something like that? I think it could also be beneficial for forks and maybe local testing.