HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hypercore-protocol
cli
JavaScript2020–2021
hypercore-protocol / cli

cli

A CLI for peer-to-peer file sharing using the Hypercore Protocol.

3Distinct people
3Mentions
0Explicit recommenders
207GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A CLI for peer-to-peer file sharing using the Hypercore Protocol.

GitHub

Where it is used

No documented product use has been verified yet.

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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 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 week3 dated mentions

Observed mentions: 2020-12-14 00:12:20 UTC to 2021-05-05 21:40:00 UTC. Weeks start Monday, UTC.

0122020-12-14 00:00:00 UTC to 2020-12-21 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsDec 142020-12-21 00:00:00 UTC to 2020-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-12-28 00:00:00 UTC to 2021-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-04 00:00:00 UTC to 2021-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-11 00:00:00 UTC to 2021-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-18 00:00:00 UTC to 2021-01-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-25 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-01 00:00:00 UTC to 2021-02-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-08 00:00:00 UTC to 2021-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-15 00:00:00 UTC to 2021-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-22 00:00:00 UTC to 2021-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 222021-03-01 00:00:00 UTC to 2021-03-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 00:00:00 UTC to 2021-03-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-15 00:00:00 UTC to 2021-03-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-22 00:00:00 UTC to 2021-03-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 00:00:00 UTC to 2021-04-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-05 00:00:00 UTC to 2021-04-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-12 00:00:00 UTC to 2021-04-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-19 00:00:00 UTC to 2021-04-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-26 00:00:00 UTC to 2021-05-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-05-03 00:00:00 UTC to 2021-05-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 3

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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 142020-12-14 00:00:00 UTC2020-12-21 00:00:00 UTC202
Dec 212020-12-21 00:00:00 UTC2020-12-28 00:00:00 UTC000
Dec 282020-12-28 00:00:00 UTC2021-01-04 00:00:00 UTC000
Jan 42021-01-04 00:00:00 UTC2021-01-11 00:00:00 UTC000
Jan 112021-01-11 00:00:00 UTC2021-01-18 00:00:00 UTC000
Jan 182021-01-18 00:00:00 UTC2021-01-25 00:00:00 UTC000
Jan 252021-01-25 00:00:00 UTC2021-02-01 00:00:00 UTC000
Feb 12021-02-01 00:00:00 UTC2021-02-08 00:00:00 UTC000
Feb 82021-02-08 00:00:00 UTC2021-02-15 00:00:00 UTC000
Feb 152021-02-15 00:00:00 UTC2021-02-22 00:00:00 UTC000
Feb 222021-02-22 00:00:00 UTC2021-03-01 00:00:00 UTC000
Mar 12021-03-01 00:00:00 UTC2021-03-08 00:00:00 UTC000
Mar 82021-03-08 00:00:00 UTC2021-03-15 00:00:00 UTC000
Mar 152021-03-15 00:00:00 UTC2021-03-22 00:00:00 UTC000
Mar 222021-03-22 00:00:00 UTC2021-03-29 00:00:00 UTC000
Mar 292021-03-29 00:00:00 UTC2021-04-05 00:00:00 UTC000
Apr 52021-04-05 00:00:00 UTC2021-04-12 00:00:00 UTC000
Apr 122021-04-12 00:00:00 UTC2021-04-19 00:00:00 UTC000
Apr 192021-04-19 00:00:00 UTC2021-04-26 00:00:00 UTC000
Apr 262021-04-26 00:00:00 UTC2021-05-03 00:00:00 UTC000
May 32021-05-03 00:00:00 UTC2021-05-10 00:00:00 UTC101

What Hacker News says

3 sources
If I want to use one of the hyper* tools to partially syncronize files p2p on a LAN, which one should I use? The hyper* world seems to be very fragmented right now. There is the dat [0] project, which started 2013 and shares files between computers p2p. In may 2020 the dat protocol was renamed to the hypercore protocol [1] and dat "will continue as the collective of teams and projects that have evolved from the original Dat CLI project.". hypercore-protocol [2] links to multiple applications for file sharing (none of them the dat CLI tool). Hyperdrive [3] "help[s] you share files quickly and safely, directly from your computer [...] -- all P2P". The github [4] mentions the hyperdrive daemon als a batteries included experience, but the hyperdrive daemon has a deprecation notice and tells you to use hyperspace. Hyperspace [5] "provides remo
Read the rest
te access to Hypercores and a Hyperswarm instance" and "exposes a simple RPC interface". The documentation is very technical and seems to be aimed at developers, not using it as a tool. Digging around in the github organisation [6] or by stumbling upon the patreon [7] one can find the hyp CLI tool which is "A CLI for peer-to-peer file sharing (and more) using the Hypercore Protocol". The first commit is 9 days old. On the twitter of the author one can also find hyperbeam [8], which is integrated into hyp. Here on HN one can also find an announcement for "uplink" [9]. The tech looks pretty cool, but the vast amount of different projects makes it difficult to grasp. From all of these tools the dat tool seems to be the most advanced, but not actively maintained. It's not linked on any of the hyper* sites and doesn't seem to be the recommended way to use the hypercore protocol to share files p2p. While I would like to use the tech, I'm pretty lost on how to do that today. [0] https://docs.datproject.org/ [1] https://blog.datproject.org/2020/05/15/dat-protocol-renamed-hypercore-protocol/ [2] https://hypercore-protocol.org/ [3] https://hypercore-protocol.org/#hyperdrive [4] https://github.com/hypercore-protocol/hyperdrive [5] https://github.com/hypercore-protocol/hyperspace [6] https://github.com/hypercore-protocol/cli [7] https://www.patreon.com/posts/hyp-command-line-44923749 [8] https://github.com/mafintosh/hyperbeam [9] https://www.patreon.com/posts/paul-reveals-is-44665610
In Hypercore protocol: a distributed (P2P) append-only log

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.