Neocities is implementing IPFS – distributed, permanent web
1–10 of 249 posts
Re: Neocities is implementing IPFS – distributed, permanent web
#2Sure, it's easier to setup your own web presence with "the cloud" today than it used to be, but this only further centralizes control of content to the big cloud providers.
Not to mention the cost of bandwidth when serving content via HTTP. Sure, you can distribute your content via BitTorrent, but what kind of user experience is that? Can my grandma use it? Probably not.
I hope IPFS sees further adoption.
Re: Neocities is implementing IPFS – distributed, permanent web
#3Re: Neocities is implementing IPFS – distributed, permanent web
#4Re: Neocities is implementing IPFS – distributed, permanent web
#5Re: Neocities is implementing IPFS – distributed, permanent web
#6Edit:
If someone like GitHub supported this for GitHub pages it would be a great step forward for this as well.
Re: Neocities is implementing IPFS – distributed, permanent web
#7Is there any incentive to host nodes?
Re: Neocities is implementing IPFS – distributed, permanent web
#8So is this primarily for static websites? I don't see dynamic websites going too well with this system. Edit: If someone like GitHub supported this for GitHub pages it would be a great step forward for this as well.
Re: Neocities is implementing IPFS – distributed, permanent web
#9Re: Neocities is implementing IPFS – distributed, permanent web
#10So is this primarily for static websites? I don't see dynamic websites going too well with this system. Edit: If someone like GitHub supported this for GitHub pages it would be a great step forward for this as well.
This is also the qualm I'm having with it... it's great for HTML files, but dynamic websites go right the window.