Thanks for clicking! Clicking 'use IPFS' makes all the images point to the local IPFS gateway on 127.0.0.1:8080, so browser can get the images from people who pin (distribute) them, like in a bittorrent. But even if you installed it, it wouldn't work because currently I don't pin image files on IPFS. IPFS daemon consumes a lot of ram and cpu resources, so I decided to shut it down.
The only thing I see when visiting the site is "An unexpected error has occurred.", despite transporting ~1.3MB of data and having all text content there in the ~5KB of initial html response... Why is web like this?! Why does it need to load highlight.js to show me the content of the page, especially since the code stuff is alrady in a <pre>?
7 comments
[ 4.0 ms ] story [ 37.5 ms ] threadNote to blog author, the 'use IPFS' link ends up pointing to 127.0.0.1, which may or may not be what was intended?
The only thing I see when visiting the site is "An unexpected error has occurred.", despite transporting ~1.3MB of data and having all text content there in the ~5KB of initial html response... Why is web like this?! Why does it need to load highlight.js to show me the content of the page, especially since the code stuff is alrady in a <pre>?