ipfs

kubo

Go2014–2026

ipfs / kubo

kubo

IPFS implementation in Go: a daemon that stores and serves content-addressed data, with a CLI, HTTP Gateway, and RPC API

Explore on GitHub Read Hacker News discussions

59Distinct people

84Mentions

1Explicit recommenders

17.2KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

IPFS implementation in Go: a daemon that stores and serves content-addressed data, with a CLI, HTTP Gateway, and RPC API

GitHub

Where it is used

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

What people are saying

reminds me of this comment: "Of these, quic is my favorite option for the future. It is a truly phenmenal transport, with tons of things done very, very well. However, though…

seoguru used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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

Also in these discussions

ipfs/ipfs · linked in 6 of the same discussions
ipfs/js-ipfs · linked in 4 of the same discussions
ipfs-inactive/faq · 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, 2:04:58 PM 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 year84 dated mentions

Observed mentions: 2014-10-18 20:16:56 UTC to 2026-08-03 20:29:31 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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	Submissions	Comments
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	1	0	1
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	10	0	10
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	8	0	8
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	11	1	10
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	10	0	10
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	12	0	12
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	8	2	6
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	9	1	8
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	6	1	5
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	4	0	4
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	0	1
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	2	0	2
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	2	2	0

What Hacker News says

8 sources

lgierth·Nov 18, 2016

Performance of adding to IPFS has improved in the past months, I recently added 3.7 TB of https://cdn.media.ccc.de and it took ~24h, admittedly these files are each pretty big, while Wikidata sounds like tons of tiny files. One more major improvement is on the way, which is directory sharding using a HAMT data structure: https://github.com/ipfs/go-ipfs/pull/3042

In WikipediaP2P

diggan·Oct 23, 2016

We're planning to use Same-origin policy to prevent this. It was first brought up here: https://github.com/ipfs/go-ipfs/issues/651 You can read more about same-origin policy here: https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...

In IPFS is the Distributed Web

haadcode·Oct 23, 2016

Unfortunately there's no proper demo page :/ We're working on improving the docs (we know this is big issues atm). There's an old version (from June) of Orbit at http://orbit.libp2p.io which you can try. Much has happened since and we're working on bringing the js-ipfs version Orbit back to a working state. Re.Pubsub, I'm personally also very excited about it! :) The specs and general info are located here https://github.com/libp2p/pubsub. go-ipfs merged pubsub into master some time ago with this commit https://github.com/ipfs/go-ipfs/commit/e1c40dfa347e38bdc9812... and we're working to get it into js-ipfs here https://github.com/ipfs/js-ipfs/issues/530.

In IPFS is the Distributed Web

haadcode·Oct 17, 2016

Developer of Orbit here. Great to hear all the feedback, thank you! Most questions have been already answered, but to clarify: Orbit indeed uses IPFS pubsub (https://github.com/ipfs/go-ipfs/pull/3202) for real-time message propagation, no servers are involved. In addition, it uses orbit-db (https://github.com/haadcode/orbit-db) - a distributed database on IPFS - for the message history, so the messages are not ephemeral and the channel history can always be retrieved. This is a really nice property and allows Orbit to work in "disconnected" or split networks, as well as offline. Orbit has been a testbed for IPFS applications and orbit-db came out of that work, enabling various types of distributed, p2p applications and use cases: comment systems, votes/likes/starring systems (with counters), feeds, etc. And now with IPFS pubsub, we're fin

Read the rest

ally at a point of being completely serverless and distributed which is hugely exciting and opens so many doors for future work! I recently gave a talk at Devcon2 about Orbit and developing distributed real-time applications (https://ethereumfoundation.org/devcon/?session=orbit-distrib...) and while the videos of the talk are not out yet (afaik coming very soon!), there's the uncut video of the talk here http://v.youku.com/v_show/id_XMTc1NjU1NzEyNA==.html?firsttim... if you're interested to learn more. Video of the demo I showed in the talk is here https://ethereumfoundation.org/devcon/wp-content/uploads/201.... I'll be hanging out on #ipfs in Orbit if you're interested to try it out. Note that the Electron app and the web version at orbit.libp2p.io don't talk to each other atm (we're working on this), so I would highly recommend to try out the Electron app. While you're at it, try drag & dropping files and folders to a channel, that's one of the coolest feature of Orbit atm imo :) We're actively developing Orbit and making a push in the next few months, if you're interested to take part in the design and development, or would like to develop your own apps using the same tech, join us on Github https://github.com/haadcode/orbit/issues. Thanks for the comments everyone, much appreciated!

In Orbit – Distributed, serverless, peer-to-peer chat application on IPFS

fizzbatter·Oct 16, 2016

Wow, thank you! Very interesting! Quite odd that none of my follows mentioned this going live, must be an issue of too many github issues. Time to dig into this a bit! edit: For anyone else perplexed and surprised by me, seems `floodsub` is their moniker for the new tech, and it was (in part) merged in here: https://github.com/ipfs/go-ipfs/pull/3202 This is really, really cool! Also, if this implementation is robust and performant, this is huge for IPFS.

In Orbit – Distributed, serverless, peer-to-peer chat application on IPFS

viraptor·Aug 12, 2016

You realise you're talking about system with 3 live implementations (one complete/reference) https://github.com/ipfs/ipfs#protocol-implementations with the reference implementation being tested on every commit on linux+osx, working on freebsd (https://www.freshports.org/sysutils/ipfs-go/), and windows (https://github.com/ipfs/go-ipfs/blob/master/docs/windows.md), right? Finding other systems left as an exercise to the OP.

In Show HN: Beaker – A browser for IPFS and Dat

whyrusleeping·Mar 23, 2016

I would start at our webpage here: https://ipfs.io/ Though admittedly it needs work. If youre the video watching type, the stanford talk on that page is very good (i recommend setting the speed to 1.5 or so). Beyond that, come check out our git repos: ipfs whitepaper and general protocol discussion: https://github.com/ipfs/ipfs go-ipfs codebase: https://github.com/ipfs/go-ipfs And the FAQ: https://github.com/ipfs/faq

In Gx: A package management tool built around IPFS

_prometheus·Mar 23, 2016

jbenet here. We're all very excited about the dev interest in gx and ipfs! thanks! we did not expect attention on it this soon! Please check it out, try it, and give us feedback! Please know though that things are still super early, and very rough! We do not think our pkg mgment efforts are UX ready for end users who want something strictly better today. But they are ready for early adopters who want to think or hack on them with us. In fact, we are now self-hosting go-ipfs in gx! https://github.com/ipfs/go-ipfs Something to bear in mind: we are building infrastructure you can rely on long term, with decentralization, flexibility, and futureproofing from the ground up. We want our protocols and tools to survive independent of fragile organizations or fragile routing. We can't take many shortcuts (like depending on centralizing agents), be

Read the rest

cause we want something rock solid to last for decades. This means it takes us a lot longer to build high perf and high quality UX, because there's a lot more to do. More work, but it is all achievable. The rough edges will disappear as we improve the tooling. Even today, gx is amazingly simple and powerful, and already does much for dependability. It's worth mentioning other package management tooling we're working on too: * NPM + IPFS - https://github.com/diasdavid/registry-mirror and other repos. This is an effort to improve how NPM works with IPFS * pacman + ipfs - https://github.com/ipfs/notes/issues/84 - this is a super rough way to show how to add ipfs support to a package manager through FUSE. it's not the best way, but it works! * also, we <3 nix, and cool stuff coming in the future there :) We have LOTS in development and store for the package manager communities. It's a very exciting time. Please join us at https://github.com/ipfs/ipfs and #ipfs and #gx on freenode IRC. And, if anyone wants to work on "Hypermodular Programming" with us, see https://github.com/jbenet/random-ideas/issues/27 and ping me :)

In Gx: A package management tool built around IPFS