ipfs

specs

HTML2015–2023

ipfs / specs

specs

Technical specifications for the IPFS protocol stack

Learning & Reference Networking

Explore on GitHub Read Hacker News discussions

11Distinct people

17Mentions

0Explicit recommenders

1.2KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Technical specifications for the IPFS protocol stack

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

ipfs-inactive/faq · linked in 2 of the same discussions
ipfs/notes · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2015-04-04 20:01:13 UTC to 2023-06-26 03:04:45 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	4	4
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	5	5
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	4	4
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	3	3
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1

What Hacker News says

4 sources

daviddias·Nov 15, 2015

Hi Alexander, this is really great! I've started `registry-mirror` to demonstrate how a Content-Addressed file structure and P2P discovery, can bring a lot of speed improvements, specially when the bottleneck is low bandwidth/latency to the backbone, by connecting to more local peers that have the content that we are looking for. Right now, the goal with `registry-mirror` is to have a very large IPFS node in the network with the entire npm and that keeps replicating it, while end user machines only download the modules they need (and if they agree, provide them to the network as well). Each end user will be able to get the latest state of the registry, through a IPNS hash, a mutable pointer, that changes each time the mirror is updated. The nix package manager model layers perfectly on top of IPFS' MerkleDAG (https://github.com/ipfs/specs

Read the rest

/tree/master/merkledag), it can be a very awesome transport for ied. An example of a package manager that uses IPFS to distribute the packages is GX https://github.com/whyrusleeping/gx - Still a WIP. If this is interesting to you, join us at IRC Freenode #IPFS, it would be great to bounce more ideas! :)

In Show HN: ied – an alternative package manager for Node

_prometheus·Sep 17, 2015

(IPFS author here) You're hitting on some really hard questions :) the gist is that you use a "record system" that has some transport guarantees, for example relying on a dht has certain kind of properties, as opposed to relying on pub/sub over trusted nodes. IPFS has this part as pluggable, though we're focusing on a large public DHT first. DHTs are pretty robust today, though yes have weaknesses we're working on. now, the key is that, on top of that, you build assurances around cryptographic freshness (i.e. "trust this record for a certain amount of time"). of course, "certain amount of time" varies with your notion of time (e.g. NTP, vs blockchain times, etc), so the user gets to set that. if you're interested in how the "record system" works and will evolve, take a look at https://github.com/ipfs/specs/tree/master/records -- though ad

Read the rest

mittedly this is not complete or exhaustive, as we have A TON to do and are focusing on pushing out reliable code.

In Hosting a simple static site on IPFS

iso8859-1·Sep 9, 2015

see https://github.com/ipfs/specs/tree/master/protocol#ipfs-and-... : "authenticated: content can be hashed and verified against the link"

In Neocities is implementing IPFS – distributed, permanent web

_prometheus·Apr 4, 2015

(EDIT: we've a meetup coming up soon. The SV Ethereum Meetup is hosting an intro to IPFS later this month in San Francisco: http://www.meetup.com/EthereumSiliconValley/events/221350594... come hang out!) --------------- Hello Everyone! --------------- @jbenet here. Thanks for all the attention! Did not expect to wake up to this post today :) The best resources for learning about ipfs are: - The IPFS Paper: http://gateway.ipfs.io/ipfs/QmR7GSQM93Cx5eAg6a6yRzNde1FQv7uL... (note: DRAFT 3, working on DRAFT 4, lots has evolved.) - The Alpha Demo: https://www.youtube.com/watch?v=8CMxDNuuAiQ - The First Tech Talk: https://www.youtube.com/watch?v=Fa4pckodM9g - The IRC Logs: http://botbot.me/freenode/ipfs/ -- there's so much knowledge in these, we're working on moving it over. We're working on a bunch of more expository media: - Specs!! https://git

Read the rest

hub.com/ipfs/specs - More Demos - More Talks - Draft 4 of the paper But there's only so many hours in a day, and we spend most of our time developing. All the resources will be way more polished as time goes on. Please bear with us as we make these available. In the meantime, ask questions in our new FAQ (below), or in #ipfs on irc.freenode.net -- And we'll be answering questions here too of course. I've just created: https://github.com/ipfs/faq -- if you ask questions there we can build a knowledge base IPFS already works-- you can install it and try it out. It's not production ready yet, but it's already very reliable. I use it to move around all sorts of personal files, and we use it to host many websites. Some people asked about what applications are there now? There's many static websites on ipfs, and some simple webapps. We ship our entire ipfs webui with ipfs itself (turtles all the way down!). In particular, Eris Industries recently made a decentralized YouTube clone using IPFS and their Decerver: https://github.com/eris-ltd/2gather If you see more-- please let us know at https://github.com/ipfs/community so we add it to an index (we just reorged our repos under the github org last week).. We need to make some more tooling to make web-publishing with ipfs really, really nice. We'll be making that over the next few weeks, so if you're interested in pushing out websites with ipfs-- come talk to us. Another big use case we're going after is Docker container distribution. We're preparing a whole bunch of demos right now that we'll show off in the next week or two. You can peek at: https://github.com/ipfs/container-demos We can already boot entire VMs and containers over ipfs in <10 seconds :D which makes me really happy. You can boot to ipfs with this makefile: https://gist.github.com/jbenet/76afa70955910a2ed097 If you want to help, the best ways are: - Come hack with us! We're particularly looking for Go hackers - Just use it! - Write applications on top. - Report issues: https://github.com/jbenet/go-ipfs/issues and so on. - Help us with docs - Write another implementation (this is blocked by https://github.com/ipfs/specs/) Some ipfs community members i've seen posting below are: whyrusleeping, dylankpowers, inconshreveable Also, IPFS development is sponsored by our company, "Protocol Labs, Inc" -- we also make Filecoin. We are hiring, so check out: http://ipn.io/join (yeah-- we just changed the company name. still need to update ipn.io / get a new domain.) See you around the tubes! :) - @jbenet

In IPFS is a new peer-to-peer hypermedia protocol