{"slug": "ipfs", "name": "IPFS", "category": "files", "category_name": "Files, sync and backup", "description": "", "recommenders": 3, "commenters": 6, "warners": 2, "score": 1.093, "rising": 0.35, "first": "2026-01-15", "latest": "2026-10-30", "why": "IPFS however is much more featureful than that. It allows to build decentralized distributed (serverless) websites and services", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 1, "compare": 0, "warn": 2}, "spark": [0, 0, 1, 0, 0, 0, 0, 0, 1, 0, 0, 1], "listed": true, "loved": [], "caveat": "", "short_quote": "IPFS however is much more featureful than that. It allows to build decentralized distributed (serverless) websites and services", "icon": true, "domain": null, "github_repo": null, "official_url": "https://ipfs.tech", "pricing": "", "aliases": ["IPFS"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 798944144, "item_id": 49934009, "url": "https://news.ycombinator.com/item?id=49934009", "by": "r3trohack3r", "date": "2026-10-02", "stance": "recommend", "quote": "adopting something that is forward compatible at the ecosystem/community level like ipfs makes sense to me", "excerpt": "Heard. If we\u2019re going through this pain of a migration- adopting something that is forward compatible at the ecosystem/community level like ipfs makes sense to me. You throw a byte at the front of the hash which indicates the format the hash is in. We have a content addressable storage system internally and we use a self describing hash for it, so we can change the hashing scheme for different use cases. Multihash is", "context": "", "use_case": "content addressing with self-describing hashes", "switched_from": "", "story": "Git 3.0's upcoming SHA-256 default will be a costly mistake"}, {"id": 780067936, "item_id": 48754246, "url": "https://news.ycombinator.com/item?id=48754246", "by": "ValdikSS", "date": "2026-07-01", "stance": "recommend", "quote": "IPFS however is much more featureful than that. It allows to build decentralized distributed (serverless) websites and services", "excerpt": "1. IPFS has addressable content The main drawback of BitTorrent v1 file hashing scheme inside the .torrent file is that it makes a virtual stream of the directory you want to share, splits that stream into blocks, and hash it altogether. That means that each file inside the torrent is unique, even if your directory have very common files, each is which exist in BitTorrent network per se. IPFS solves this issue by jus", "context": "", "use_case": "decentralized content distribution", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}, {"id": 780063792, "item_id": 48753987, "url": "https://news.ycombinator.com/item?id=48753987", "by": "ValdikSS", "date": "2026-07-01", "stance": "recommend", "quote": "It is a huge server traffic saver.", "excerpt": "I use it for about 5 years, to publish javascript file (proxy auto-configuration) and serve the contents over different gateways. It is a huge server traffic saver. Used to use it to host different static websites on custom domains while Cloudflare's gateway was working, stopped using it for this purpose since its sunset in 2024. Neocities used to publish their websites over IPFS, this feature got broken (for years) ", "context": "uses IPFS in production for about 5 years", "use_case": "serving proxy auto-config JS file", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}, {"id": 746191104, "item_id": 46636944, "url": "https://news.ycombinator.com/item?id=46636944", "by": "notepad0x90", "date": "2026-01-15", "stance": "recommend", "quote": "if they moved the back-end to a distributed system, like ipfs perhaps? that would be amazing", "excerpt": "If you use wikipedia as a starting point, and actually check reference material critically, it's invaluable in my opinion. We used to have to pay lots of money for encyclopedias for less quality. My hope is that while I think the website/webapp itself doesn't need much change, if they moved the back-end to a distributed system, like ipfs perhaps? that would be amazing. Even if wikipedia is blocked, or tampered with, ", "context": "", "use_case": "distributed hosting of Wikipedia", "switched_from": "", "story": "25 Years of Wikipedia"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 804934433, "item_id": 50308402, "url": "https://news.ycombinator.com/item?id=50308402", "by": "rhodey", "date": "2026-10-30", "stance": "warn", "quote": "IPFS has been very very poorly maintained.", "excerpt": "This is the same style of attack that took 1.5B from Bybit ~1yr ago. Fundamentally: There is no way to lock webapps to reproducible builds. Except: IPFS could do it but IPFS has been very very poorly maintained. I published IPFS-boot ~1yr ago and its a simple idea: 1. deploy a webapp bootloader using something immutable like IPFS 2. bootloader is basically react hot reloading except user agrees what to load 3. bootlo", "context": "", "use_case": "immutable webapp hosting", "switched_from": "", "story": "Polymarket 1h halt after vendor compromise; affected users will be 'made whole'"}, {"id": 780026272, "item_id": 48751642, "url": "https://news.ycombinator.com/item?id=48751642", "by": "Borg3", "date": "2026-07-01", "stance": "warn", "quote": "IPFS is a bit disappointement", "excerpt": "Yeah.. IPFS is a bit disappointement. I was a bit exceited about it back in the day. Recently, I wanted to download sth large from archive.org, I used torrent (and my legacy torrent client) and it worked like a charm! It seems pure HTTP tracker + Torrent is good enough.", "context": "", "use_case": "", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}]}], "who": [{"by": "bergie", "context": "worked at a website builder", "url": "https://news.ycombinator.com/item?id=48757414", "date": "2026-07-01"}, {"by": "ValdikSS", "context": "uses IPFS in production for about 5 years", "url": "https://news.ycombinator.com/item?id=48753987", "date": "2026-07-01"}], "tags": [], "use_cases": ["immutable webapp hosting", "content addressing with self-describing hashes", "distributing content between clusters", "decentralized content distribution", "serving proxy auto-config js file", "distributed hosting of wikipedia"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48748518", "title": "How We Made IPFS Content Publishing 10x Faster", "mentions": 4}, {"url": "https://news.ycombinator.com/item?id=50305225", "title": "Polymarket 1h halt after vendor compromise; affected users will be 'made whole'", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49924179", "title": "Git 3.0's upcoming SHA-256 default will be a costly mistake", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46632023", "title": "25 Years of Wikipedia", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {"warn": 1, "recommend": 1, "neutral": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {"recommend": 1, "warn": 1}}, "quotes": [{"id": 804934433, "item_id": 50308402, "url": "https://news.ycombinator.com/item?id=50308402", "by": "rhodey", "date": "2026-10-30", "stance": "warn", "quote": "IPFS has been very very poorly maintained.", "excerpt": "This is the same style of attack that took 1.5B from Bybit ~1yr ago. Fundamentally: There is no way to lock webapps to reproducible builds. Except: IPFS could do it but IPFS has been very very poorly maintained. I published IPFS-boot ~1yr ago and its a simple idea: 1. deploy a webapp bootloader using something immutable like IPFS 2. bootloader is basically react hot reloading except user agrees what to load 3. bootlo", "context": "", "use_case": "immutable webapp hosting", "switched_from": "", "story": "Polymarket 1h halt after vendor compromise; affected users will be 'made whole'"}, {"id": 798944144, "item_id": 49934009, "url": "https://news.ycombinator.com/item?id=49934009", "by": "r3trohack3r", "date": "2026-10-02", "stance": "recommend", "quote": "adopting something that is forward compatible at the ecosystem/community level like ipfs makes sense to me", "excerpt": "Heard. If we\u2019re going through this pain of a migration- adopting something that is forward compatible at the ecosystem/community level like ipfs makes sense to me. You throw a byte at the front of the hash which indicates the format the hash is in. We have a content addressable storage system internally and we use a self describing hash for it, so we can change the hashing scheme for different use cases. Multihash is", "context": "", "use_case": "content addressing with self-describing hashes", "switched_from": "", "story": "Git 3.0's upcoming SHA-256 default will be a costly mistake"}, {"id": 780118624, "item_id": 48757414, "url": "https://news.ycombinator.com/item?id=48757414", "by": "bergie", "date": "2026-07-01", "stance": "neutral", "quote": "we used IPFS for distributing content between our serving clusters.", "excerpt": "Back when I was working at a website builder, we used IPFS for distributing content between our serving clusters. If also made the sites available on IPFS, but that was a secondary concern.", "context": "worked at a website builder", "use_case": "distributing content between clusters", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}, {"id": 780067936, "item_id": 48754246, "url": "https://news.ycombinator.com/item?id=48754246", "by": "ValdikSS", "date": "2026-07-01", "stance": "recommend", "quote": "IPFS however is much more featureful than that. It allows to build decentralized distributed (serverless) websites and services", "excerpt": "1. IPFS has addressable content The main drawback of BitTorrent v1 file hashing scheme inside the .torrent file is that it makes a virtual stream of the directory you want to share, splits that stream into blocks, and hash it altogether. That means that each file inside the torrent is unique, even if your directory have very common files, each is which exist in BitTorrent network per se. IPFS solves this issue by jus", "context": "", "use_case": "decentralized content distribution", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}, {"id": 780063792, "item_id": 48753987, "url": "https://news.ycombinator.com/item?id=48753987", "by": "ValdikSS", "date": "2026-07-01", "stance": "recommend", "quote": "It is a huge server traffic saver.", "excerpt": "I use it for about 5 years, to publish javascript file (proxy auto-configuration) and serve the contents over different gateways. It is a huge server traffic saver. Used to use it to host different static websites on custom domains while Cloudflare's gateway was working, stopped using it for this purpose since its sunset in 2024. Neocities used to publish their websites over IPFS, this feature got broken (for years) ", "context": "uses IPFS in production for about 5 years", "use_case": "serving proxy auto-config JS file", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}, {"id": 780026272, "item_id": 48751642, "url": "https://news.ycombinator.com/item?id=48751642", "by": "Borg3", "date": "2026-07-01", "stance": "warn", "quote": "IPFS is a bit disappointement", "excerpt": "Yeah.. IPFS is a bit disappointement. I was a bit exceited about it back in the day. Recently, I wanted to download sth large from archive.org, I used torrent (and my legacy torrent client) and it worked like a charm! It seems pure HTTP tracker + Torrent is good enough.", "context": "", "use_case": "", "switched_from": "", "story": "How We Made IPFS Content Publishing 10x Faster"}, {"id": 746191104, "item_id": 46636944, "url": "https://news.ycombinator.com/item?id=46636944", "by": "notepad0x90", "date": "2026-01-15", "stance": "recommend", "quote": "if they moved the back-end to a distributed system, like ipfs perhaps? that would be amazing", "excerpt": "If you use wikipedia as a starting point, and actually check reference material critically, it's invaluable in my opinion. We used to have to pay lots of money for encyclopedias for less quality. My hope is that while I think the website/webapp itself doesn't need much change, if they moved the back-end to a distributed system, like ipfs perhaps? that would be amazing. Even if wikipedia is blocked, or tampered with, ", "context": "", "use_case": "distributed hosting of Wikipedia", "switched_from": "", "story": "25 Years of Wikipedia"}]}