HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hyphanet
wiki
Emacs Lisp2017–2026
hyphanet / wiki

wiki

Discover this repository through its Hacker News conversations.

5Distinct people
6Mentions
0Explicit recommenders
86GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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

Observed mentions: 2017-10-02 00:22:44 UTC to 2026-05-05 16:40:23 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-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): 3 mentions; 0 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* 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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
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 UTC303
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 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

3 sources
Freenet's default feature is HTML sites - just like the regular web but fully hosted on Freenet and only accessible through it. The content of those sites is whatever their authors want it to be :) Further, dynamic applications such as forums are also available. Here's a list of apps built on top of Freenet: https://github.com/freenet/wiki/wiki/Projects Freenet needs UDP so it likely won't work on Tails as Tails tunnels everything through Tor - which does not support UDP AFAIK.
In Freenet is a peer-to-peer platform for censorship-resistant communication
Freenet development is NOT dead! :) I have been contributing for ~ 12 years and now have acquired long-term funding (independent of Freenet's own funding!) to continue my contributions in a more intense fashion. The core network which serves static HTML sites + audio/video is stable and usable. It has a bunch of reliable long-term contributors working on it. Hence development on my personal side is focused on polishing existing dynamic applications which are built on top of Freenet, and implementing some new ones. Basic implementations of notably forums, social networking, blogging and mail exist already, the goal is to make them easy to use (integrate them into the main UI instead of being standalone), add much more features, improve performance and security. Here's a list of these and dozens of other apps built on Freenet: https://gith
Read the rest
ub.com/freenet/wiki/wiki/Projects Developing dynamic stuff is taking so long because it is a complex endeavor: On the regular Internet, censorship happens by "look up who owns the IP, go to their address, remove the computer." Since this is not possible on Freenet as everyone is anonymous, censorship will happen by denial of service: For example forum systems would be spammed to death to get rid of unwanted content. Thus the architecture of censorship-resistant systems has to be reinvented from scratch, you can't just take a regular forum system and stick Freenet on top of it. It has to be decentralized to be resistant against DoS - there must not be Tor-alike central servers ("hidden sites" / .onion sites). Instead messages are stored across the whole network and replicated automatically if they are downloaded more often and thus need more bandwidth (the added redundance also makes them more censorship-resistant). And spam filtering need to be a first-class application, I have worked for years only on that. So the different architecture is the primary pitfall which many projects which decided "Freenet is too old, we're gonna build this from scratch with nice Javascript etc." fell into IMHO: First it's "we'll develop a regular app, we can bolt Tor onto it later", then they realize that the threat-model is so different that this is just not possible and the projects never become anonymous/censorship-resistant. So privacy needs to be built in from the start. Luckily, Freenet did that right (even though it was the first anti-censorship + privacy network!), and I don't mind that it's taking decades to develop because of the extended threat model: That's still better than being one of wheel-reinventing post-Freenet projects which then abandon the privacy idea in the end anyway, or postpone it forever.
In Freenet is a peer-to-peer platform for censorship-resistant communication

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.