The author reflects on their experience with IPFS+ENS websites, highlighting their early involvement and various projects related to this decentralized technology. They initially believed that peer-to-peer websites would be robust, censorship-resistant, and scalable, but in practice, they encountered challenges. Many IPFS users rely on gateways instead of running their own nodes, and even if someone does run their own node, it doesn’t guarantee that they will pin a website’s content. Dynamic websites and the lack of easy commands to pin the latest content further complicate matters. The author also discusses their difficulties in getting their IPFS blog to be reliably available in different browsers and gateways. They mention discovering cid.contact, a service that helps with content routing, but raise concerns about its centralization. Ultimately, the author moved their blog back to a traditional server due to the ongoing struggles with IPFS. They maintain their admiration for IPFS but acknowledge that it currently doesn’t meet their personal blog’s needs.
https://neimanslab.org/2024-01-31/why-i-moved-my-blog-ipfs-to-server.html