6 ms·
The author claims that IPFS enables a "permanent web" and eliminates 404-like experiences. How does IPFS guarantee that all published content will be available
by CharlesW 5y ago
The author claims that IPFS enables a "permanent web" and eliminates 404-like experiences. How does IPFS guarantee that all published content will be available forever? (In my beginner-level knowledge of IPFS, this is the first I've heard that claim. It seems absurd.)
- leesalminen 5y agoI wonder if it could make running a service like archive.org easier. Or if it could allow for a distributed archive.org service where nerds worldwide can contribute x GB storage to the cause?
- Sargos 5y agoThis is one of the biggest stated use cases of IPFS as it effectively replaces archive.org with a better version that is more distributed, has better uptime, and more importantly has a much larger and nearly complete and pristine version of the entire internet for conceivably as long as the internet itself exists.
- acdha 5y agoIt does only the first of those things: using content hashes means that anyone can populate an archive which is easily discovered. For the rest, hosting takes money. People will not archive the entire internet for free and IPFS is not a magic wand which eliminates the need to have people like the skilled IA team. It could make their jobs easier but that’s far from “nearly complete” and no more or less pristine.
- naasking 5y agoIt gives you the tools to build an archive.org equivalent using volunteer storage though, rather Than asking for monetary donations. All you need is a database of known content hashes and a database of volunteers and you randomly distribute content among volunteers and periodically ensure a minimum number of clients are replicating each known hash.
- acdha 5y ago“All you need” is only true at the highest level: IPFS gives you a great way to discover replicated content. It doesn't help you know that the list of known hashes is complete (consider how much work IA has spent making sure that they crawl sites completely enough to be able to replay complex JavaScript), handle the scale of that list (this is a VERY large database which updates constantly), or provide networked storage at a scale measured in the hundreds of petabytes. Volunteer capacity at the scale of many petabytes of online storage is unproven and the long tail of accesses is enough that you're going to have to think not just about the high replication factor needed but also the bandwidth available to serve that content on a timely manner and rebuild a missing replica before another fails.
- naasking 5y ago> It doesn't help you know that the list of known hashes is complete Right, which is why I said it would have to periodically scan the registered clients to ensure a minimum number of clients has each block to ensure redundancy. > also the bandwidth available to serve that content on a timely manner and rebuild a missing replica before another fails. I think a slow, cheap but reliable archive is better than "more expensive but lower latency", so I'm not particularly concerned with timeliness.
- acdha 5y ago> > It doesn't help you know that the list of known hashes is complete > Right, which is why I said it would have to periodically scan the registered clients to ensure a minimum number of clients has each block to ensure redundancy. That's the easy problem, not the hard one I was referring to: doing what IA does requires you to be able to crawl web resources and identify everything which needs to be available for a page snapshot to be usable. IPFS only helps with that in the sense that you can tell whether you have the same URL payload without requesting it — you still need to handle dynamic behaviour and that's most of the work. > I think a slow, cheap but reliable archive is better than "more expensive but lower latency", so I'm not particularly concerned with timeliness. What I would be concerned with is “more expensive, higher latency, and greater risk of irrecoverable failure”. Relying on volunteers means that you need far more copies because nobody has a commitment to provide resources or even tell you if they decide to stop (“ooops, out of space. Let me clear some up — someone else must have this…”), and the network capacity isn't just a factor for user experience — although that can prevent adoption if it's too slow — but more importantly because it needs to be available enough to rebuild missing nodes before other ones also disappear.
- somenewaccount1 5y agoAnd quite annoyingly, it's the opposite of how IPFS works. IPFS nodes only cache the content as long as it's actively requested. Depending on the cache policy of the node, this can be as short as 24 hours. Yes, it could still exist on your private node that your running from your laptop, but this is the equivalent of saying that all published content is available forever because it's on your hard drive. Honestly, I like IPFS as a tech, and blockchain isn't useless, but the entire community just makes me want to puke because it's full of so many extremely ignorant people (at best), but mostly just fraudulent liars (at worse and most common).
- chriswarbo 5y ago> Yes, it could still exist on your private node that your running from your laptop, but this is the equivalent of saying that all published content is available forever because it's on your hard drive. No, the difference is that IPFS will use the same address to fetch content from anyone who's seeding it. If Hacker News shuts down, it will no longer be accessible at 'news.ycombinator.com'; all existing links to that address will die, or worse will start showing some unrelated content (probably domain-squatter spam). That cannot be prevented by making a copy on my hard drive (or even the Wayback Machine). On the other hand, an IPFS version will continue to exist at the same address for as long as anyone is seeding it. All links will remain working; anyone can join in the hosting if they like; even if it eventually stops getting seeded, it may still re-appear if someone re-inserts it, e.g. if they insert the contents an old hard drive they found in an attic (as long as the same hash algorithm is used, then the address will stay the same).
- jayd16 5y agoDoesn't a forum need things like user login? Is there an example of such a thing as a forum existing fully on IPFS?
- chriswarbo 5y ago> Doesn't a forum need things like user login? I was only talking about the HTML, not the backend server code. Still, you could look on https://awesome.ipfs.io/apps https://awesome.ipfs.io/apps for ideas.
- jFriedensreich 5y agoits more that ipfs enables a permanent web, not that this technology immediately has this property as a feature. it requires players like internet archive, libraries, website hosters and individuals to pin content and develop interesting pinning strategies. for example browsers could pin everything that is bookmarked and everything that is in browser cache.
- 6510 5y agoYou can link to documents and keep them online as oppose to publications with unobtainable references.
- delaaxe 5y agoI don't know about IPFS but Arweave solved the "permanent" part by asking nodes to periodically prove that they're actually storing what they're supposed to be storing: https://www.arweave.org/ https://www.arweave.org/
- Jasper_ 5y agoWhat happens when the servers then fail to provide that promise? Isn't the data lost?
- mmahemoff 5y agoThe idea is to incentivise hosting via crypto - with ARWeave, there's a bigger upfront fee but no ongoing fees. In theory, it's meant to secure 200 years of storage by putting aside most of the upfront fees for later and (conservatively) assuming storage costs decrease by at least 0.5% per year.
- delaaxe 5y agoIf the servers do provide the proof, they get a reward, if they can't, they loose part of their collateral (also called stake).
- pfraze 5y agoThe IPFS version of Arweave is Filecoin
- SavantIdiot 5y agoSimple: you set up a few centralized servers with backups...
- diegocg 5y agoBasically with ipfs you try to download some content by referring to it by a hash. This means that the content will be available forever - as long as there is someone willing to cache that content. Which is, obviously, something that won't always happen. But it _can_ theoretically happen, so people with a cache of some old web page may revive it, even after the original site is gone.
- kzrdude 5y agoHow do you refer to something "by name"? Let's say the current version of Wikipedia's article on Lagrange multiplier - the data is changing, so can't use a hash of the content.
- sodality2 5y agoThe hash is not a literal hash of the content- I think it's like a key that lets anyone looking for it ensure it's legitimate. Then the IPFS p2p search mechanism is what lets you find it.
- drdeca 5y agoIn what sense is it not a literal hash? Because it had the prefix at the start to specify what hash to use and the length?
- grumbel 5y agoIPFS doesn't give you any guarantees about if the content is actually stored anywhere, it however gives you reasonable guarantees that the addresses for that content stay the same. Meaning if somebody finds an old backup tape decades down the road, they can just stuff it back onto IPFS and all the dead links start functioning again. That's something that is impossible with HTTP, as there isn't even a guarantee that the same URL will return the same content when you access it twice. With IPFS anybody can mirror the content and keep it alive as long as they want, they don't have to hope that the server that hosts it right now keeps running. That said, IPFS isn't quite perfect here, as IPFS hashes do not actually point to the content itself, they point to a package that contains the content and depending on how that package was build, the hash will change.
- fabianhjr 5y agoOne of the spinouts of IPFS is Multiformats, particularly multihashes. It is a standard to describe hashes and provide interop: https://multiformats.io/multihash/ https://multiformats.io/multihash/ (Or the IPNS dnslink: http://multiformats.io.ipns.localhost:8080/multihash/ http://multiformats.io.ipns.localhost:8080/multihash/ )
- zozbot234 5y agoSeems like this pointlessly duplicates the "Naming things with hashes" ni: and nih: URI schemes, standardised as https://tools.ietf.org/html/rfc6920 https://tools.ietf.org/html/rfc6920 . (IPFS actually uses a proprietary "package" representation as parent points out, so there's little harm in it not using ni: URI's. But standard hashes of the underlying resource should use those. "Magnet" links are similarly problematic, but these at least support a few convenience features.)
- warkdarrior 5y ago> Seems like this pointlessly duplicates the "Naming things with hashes" ni: and nih: URI schemes Wow, they have an URI scheme for Not Invented Here. Amazing!
- 5y ago
- cma 5y agoThe claims are too strong, but it is strictly more available than today: if the original host stays it is guaranteed to stay, same as today. If they disappear, it may stay, which is stronger than today (ignoring internet archive).
- davidgerard 5y agoIt absolutely guarantees nothing of the sort. A big problem in the NFT space of late is that OpenSea sells NFTs that link to an IPFS URL, then doesn't bother seeding the image after it's sold - so a pile of NFT images no longer exist anywhere on the IPFS. https://www.vice.com/en/article/pkdj79/peoples-expensive-nfts-keep-vanishing-this-is-why https://www.vice.com/en/article/pkdj79/peoples-expensive-nft...
- noway421 5y agoOne benefit is that you or anyone for that matter can seed NFT images on IPFS. You also gotta look into the smart contract code and see if baseURI an IPFS link or someone's proprietary website.
- meltedcapacitor 5y agoIsn't that a feature? Some NFTs are hashes of recordings of destroying some physical piece of art. Surely the next level is for NFT of jpegs where only the hash is left! It will be the next big thing to go to the moon! The uncertainty about someone finding a forgotten copy adds incredible depth to the sport.
- Semiapies 5y agoIt's the fundamental lie of IPFS. IPFS people will jump in and say that it's not a lie, what they're actually saying is yadda yadda, but then they turn around and say exactly that five minutes later. It's the motte-and-bailey ( https://en.wikipedia.org/wiki/Motte-and-bailey_fallacy https://en.wikipedia.org/wiki/Motte-and-bailey_fallacy ) of IPFS. In a world of finite storage, nobody's going to keep up a copy of everything. Nobody will have a copy of most things. Even if IPFS worked acceptably, even if it worked as very narrowly promised, plenty of stuff would fall off the web. At best, we'd see somewhat fewer temporary disruptions of very currently popular content.
- ozim 5y agoYeah in the article there is an example of a video that was downloaded multiple times. That is so inefficient because "HTTP". Solution for it becoming more efficient is that someone else should host it for you ideally for free. It is just exercise in throwing big numbers and utter ignorance to impress people but downloaded megabytes are not magically going away. Just like torrents - no one wants to seed or pay hosting costs everyone wants to download. There is no protocol that is going to fix that. Why is everyone mining BTC like crazy, because they get money for that