HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
paullouisageneau
libdatachannel
C++2019–2025
paullouisageneau / libdatachannel

libdatachannel

C/C++ WebRTC network library featuring Data Channels, Media Transport, and WebSockets

5Distinct people
16Mentions
0Explicit recommenders
2.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

C/C++ WebRTC network library featuring Data Channels, Media Transport, and WebSockets

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

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

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 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 year16 dated mentions

Observed mentions: 2019-09-08 18:42:03 UTC to 2025-07-15 02:58:02 UTC.

02462019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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): 6 mentions; 0 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
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 UTC606
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

1 sources
I've looked into this the other month. There are a number of obfuscation networks that have tried this to some extent (including IPFS and GNUnet), but I am yet to find a network that works exactly as you've described: where you can just access a "tor web portal" in your browser or something. I think an obstacle would be preventing fingerprinting inside a non-fingerprint-proof browser. You might be able to do this if you ported something like tor's fingerprint-proof browser to emscripten and have it render to an HTML canvas! So far Tor has implemented WebRTC[0], but that's just for bridging to their main network. [0] https://snowflake.torproject.org/ P.S. I've also considered the "decentralized p2p social media" idea myself, but mostly because I believe the ideas we have currently behind online voting, ranking and moderation are completely
Read the rest
at odds with IRL discussions which are P2P and based on "forwarding" ideas to known peers (friends, family, community members, countrymen) rather than posting and ranking content with anonymous peers (which are susceptible to Sybil attacks). The fact that so much discussion takes place on corporate-owned forums (Including this one, regardless of how benevolent ycombinator may be) presents a major threat to democracy in general. Instead of "liking" or "upvoting" a post on a centralized forum, why not "rehost" or "forward" a post on a decentralized forum: essentially seeding it like in BitTorrent or "pinning" it in IPFS. "Followers" of a user donate their storage and bandwidth to them, combating bureaucratic attacks like delisting and DDoS against popular users. If you could port IPFS to run completely in a browser you would have this complete "pseudo-social-media" functionality. They have something called "IPNS" where instead of giving someone the hash of a file like in BitTorrent's DHT, you could give them a public key which you use to sign the latest version of a file that is to be fetched. The Public/Private keypair could represent a user's identity, and the file in this case could be a blog or account page which is updated with new links to the user's posts, or links to other user's posts. So if you ported IPFS to work within a web browser, it would just be a matter of implementing a user-interface. Boom, social media solved. You could maintain parity between desktop and web versions by using libraries like libdatachannel[1] and datachannel-wasm[2] [1] https://github.com/paullouisageneau/libdatachannel [2] https://github.com/paullouisageneau/datachannel-wasm
In Your compliance obligations under the UK’s Online Safety Bill

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.