Live data from Hacker News

Neocities is implementing IPFS – distributed, permanent web

ipfs.io

1–10 of 249 posts

Re: Neocities is implementing IPFS – distributed, permanent web

#2
Awesome writeup!

Sure, 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

#5
Reading this felt kind of like the first time I read a writeup on Bitcoin. There's the same sense of throwing out some old, formerly immutable rules here, the excitement of something that's going to test some boundaries and inevitably clash with some authority (how can you, for instance, comply with the EU's "right to be forgotten" when that information is scattered into a redundant mesh?). Interesting times ahead for IPFS.

Re: Neocities is implementing IPFS – distributed, permanent web

#8

So 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.

Re: Neocities is implementing IPFS – distributed, permanent web

#10
post #8

So 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.

I believe they have an "IPNS" protocol which is intended to handle mutations.
Post reply on HN