Some practical hints for setting up #ipfs hosted websites
Just wondering: if you publish a website to #ipfs often what's the best strategy?
1) `ipfs add -r website/`, address using recent CID and set it in DNS using `dnslink`
2) publish recent CID into IPNS (`ipfs name publish CID`)
3) Something else?
Option 1) sucks because each change to website requires updating CID in my website's reverse proxy and DNS.
Option 2) sucks because IPNS so is slooow on both publishing and resolving...
HTTP -> https://webcookies.pub/
IPFS -> /ipfs/QmcUqsb9DSwjFHVzLyT6u6TrDSzwh3BfF5qDgSnAiMpJNZ/
ENS -> webcookies.eth (you need Almonit or MetaMask browser add-on)
Yggdrasil -> http://y.webcookies.pub/
DAT -> dat://ssb.webcookies.pub/
New Malware Lays P2P Network on Top of IPFS https://www.securityweek.com/new-malware-lays-p2p-network-top-ipfs%E2%80%99 #ipfs #malware
Polish expat into UK. Information security engineer. Caver & cave rescuer (thus the bat). NHS volunteer & blood donor.