4 ms·

I didn't know about this, looks really interesting! How large are the chances that this could replace HTTP and when could that realistically happen?

libeclipse 10y ago
Not very high. They're designed to do different things. For example, IPFS only allows raw files and client-sidr code. This is not suitable for e-commerce websites or businesses, but very suitable for open-source and informational websites. They solve different problems, so shouldn't be confused. Maybe someday in the future, IPFS could be integrated into browsers for a seamless experience between the two technologies, and that'd be pretty cool.
- maxekman 10y ago
  That sound very cool indeed.
- scalio 10y ago
  Benet said in a talk that they're working on making e-commerce work in distributed systems. Ethereum for instance does exactly that.
viraptor 10y ago
Replace? None. Ipfs does not provide privacy which eliminates it from any direct http->ipfs conversions that require typical login. (You could potentially rearchitect the service, but that's not trivial) But for some specific use cases, it's pretty good. Here are some examples: https://github.com/ipfs/awesome-ipfs/blob/master/README.md https://github.com/ipfs/awesome-ipfs/blob/master/README.md
- maxekman 10y ago
  Thanks, that's a good write up. The wiki use case looks interesting!
espadrine 10y ago
The Web is heavily mutable. You are often logged in, changing pages just so; forums and chats mutate heavily; you send cookies and other sensitive information to servers… IPFS is content-addressed. The only mutable part is IPNS, which allows making a node ID point to any immutable content-addressed object. That means that any mutation requires reaching a worldwide consensus among nodes, and recomputing the hash of all its content, which for large directories with frequent updates is prohibitive, and sometimes architecturally nightmarish. Think of Twitch.tv: the video stream can't be hashed, since it is constantly updated, and the chat can have very frequent updates, and the whole chat stream needs to be re-hashed constantly (let alone the need for several feeds, so that moderators can perform validation, which again requires each of them to have their own IPNS endpoint)… But for the niche of Web publishing, it is amazing: you have a blog or news site updated, say, once every hour, and you get a CDN for free from all your users. Still, that requires the Protocol Labs team to come up with a front-end product that end-users will actually install.

libeclipse 10y ago

Not very high. They're designed to do different things. For example, IPFS only allows raw files and client-sidr code. This is not suitable for e-commerce websites or businesses, but very suitable for open-source and informational websites. They solve different problems, so shouldn't be confused. Maybe someday in the future, IPFS could be integrated into browsers for a seamless experience between the two technologies, and that'd be pretty cool.

maxekman 10y ago
That sound very cool indeed.
scalio 10y ago
Benet said in a talk that they're working on making e-commerce work in distributed systems. Ethereum for instance does exactly that.

viraptor 10y ago

Replace? None. Ipfs does not provide privacy which eliminates it from any direct http->ipfs conversions that require typical login. (You could potentially rearchitect the service, but that's not trivial) But for some specific use cases, it's pretty good. Here are some examples: https://github.com/ipfs/awesome-ipfs/blob/master/README.md https://github.com/ipfs/awesome-ipfs/blob/master/README.md

maxekman 10y ago
Thanks, that's a good write up. The wiki use case looks interesting!

espadrine 10y ago

The Web is heavily mutable. You are often logged in, changing pages just so; forums and chats mutate heavily; you send cookies and other sensitive information to servers… IPFS is content-addressed. The only mutable part is IPNS, which allows making a node ID point to any immutable content-addressed object. That means that any mutation requires reaching a worldwide consensus among nodes, and recomputing the hash of all its content, which for large directories with frequent updates is prohibitive, and sometimes architecturally nightmarish. Think of Twitch.tv: the video stream can't be hashed, since it is constantly updated, and the chat can have very frequent updates, and the whole chat stream needs to be re-hashed constantly (let alone the need for several feeds, so that moderators can perform validation, which again requires each of them to have their own IPNS endpoint)… But for the niche of Web publishing, it is amazing: you have a blog or news site updated, say, once every hour, and you get a CDN for free from all your users. Still, that requires the Protocol Labs team to come up with a front-end product that end-users will actually install.