Why I Moved My Blog from IPFS to a Server
AI summary of the linked articleNeiman, an early adopter of IPFS and ENS websites, moved his personal blog from IPFS back to a server, which he says is a simple, classic working solution for now. He says IPFS's peer-to-peer model did not work in practice because most users rely on gateways rather than running nodes or pinning content. He also describes problems with dynamic content, since IPNS and ENS updates require pinners to follow changes, and with browser access, where Helia reached his content only through the cid.contact routing service. He says the blog now runs on Jekyll on a $10 server, and he still calls himself an IPFS fan. |
 |
Recommended by 1 curator |
3 comments I’ve been in love with IPFS since 2020. I also run several small sites on IPFS and pin them on my own Kubo node that runs on a Pi4. Also I pin all my own art and all the art I collected. I recognize the issues addressed in the blog regarding updating the website and IPNS. So if you start with IPFS, start small, like for example a link tree. For example my own is on IPFS https://mishaderidder.eth.limo Anyway encourage everyone to experiment with IPFS! And run a node and pin stuff you like and want to support. You can easily run a node on your laptop or it’s even built in Brave browser, just switch it on. Here’s a tutorial to run on a Pi4. https://friendsoflittleyus.nl/how-to-install-ipfs-node-on-raspberry-pi-4-running-ubuntu/  Interesting comment Misha! Maybe you should publish on how you’re running your setup! I‘m surprised the author of the post had insightful but negative things to say, although, I have to agree that IPFS actually has a rather tricky problem with content routing because of its technical architecture. The article almost made me a little worried! Wow, didn't know I could set up an IPFS node in Brave. Just did that; if anyone was interested, there's a slick tutorial here: https://www.makeuseof.com/how-to-set-up-and-use-ipfs/ |