HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
holepunchto
hyperbeam
JavaScript2020–2024
holepunchto / hyperbeam

hyperbeam

A 1-1 end-to-end encrypted internet pipe powered by Hyperswarm

4Distinct people
4Mentions
0Explicit recommenders
549GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A 1-1 end-to-end encrypted internet pipe powered by Hyperswarm

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, 3:56:07 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 year4 dated mentions

Observed mentions: 2020-12-13 15:27:49 UTC to 2024-04-04 04:42:13 UTC.

0122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024

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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC211
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110

What Hacker News says

4 sources
It took me a minute to realize this, but HyperShell seems to be (or can be thought of as) a demo app for the (previously unknown to me) "hyper ecosystem"---Hyperswarm, Hypercore, Hyperdrive, etc: https://docs.holepunch.to/ . Perhaps an even tighter example than HyperShell is hyperbeam [1]: look at the usage section and API, and then note that it's all implemented in like 200 lines of code. I'm no expert in this field, but this stuff looks like legos for cutting-edge P2P solutions. I think this is the coolest thing I've seen since Tailscale. [1]: https://github.com/mafintosh/hyperbeam
In HyperShell: Spawn shells anywhere. Fully peer-to-peer
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.