Add Hidden Lake to Anonymity networks

[number571]

Type

Addition

---

Changes

Add Hidden Lake to Anonymity networks

---

Supporting Material

Git repo: https://github.com/number571/hidden-lake
White paper: https://github.com/number571/hidden-lake/blob/master/docs/hidden_lake_anonymous_network.pdf
Other works: https://github.com/number571/go-peer/blob/master/docs/general_theory_of_anonymous_communications.pdf

---

Affiliation

Author of the project

---

Checklist

• I have read the Contributing guide, and confirmed my PR aligns with the requirements
• I have performed a self-review (valid Markdown formatting, spelling, and grammar)
• I have indicated whether I have any affiliation with any software / services added
• I agree to follow the repositories Contributor Covenant Code of Conduct

[liss-bot]

Hello @number571

Thank you for contributing to Awesome Privacy! We will review your submission shortly. In the meantime, please ensure all changes are correct and inline with our Contributing Requirements.

Our automated checks detected some issues:

• Do not edit the README directly. This file is auto-generated from the content in awesome-privacy.yml, and so your changes will be overridden! Instead, only modify the YAML file, and be sure to follow our Contributing Guidelines.

^{🤖 I am a bot, and sometimes make mistakes. If you feel that any info here is incorrect or inaccurate, feel free to add a comment below with any corrections or justifications. This bot does not use AI, and just runs preliminary validation checks against submission requirements. Human review is still needed.}

Summary of Changes:

• Added Hidden Lake in Networking → Anonymity Networks
• Modified section metadata (furtherInfo) in Networking → Anonymity Networks

Submission Info

Repo Stats

• 🟢 License: MIT License
• 🟢 Repo Age: 7 years, 3 months
• 🟢 Last Updated: today
• 🟢 Releases: 11+
• 🟠 Stars: 253
• 🟠 Contributors: 7
• 🟢 Is Fork: No
• 🟢 Is Archived: No
• ⚪ Security Alerts: Unknown
• 🟢 Vibe Coded: 0 AI commits
• 🔵 Commits: 100+
• 🔵 Open Issues: 6
• 🔵 Website: https://github.com/number571/hidden-lake/blob/master/docs/hidden_lake_anonymous_network.pdf
• 🔵 Author: number571
• 🔵 Languages: Go, Shell, Makefile, Dockerfile

Website Checks

• 🟠 Skipped web checks, since repo URL was submitted instead of a website

^{The above data does not determine a submissions eligibility. Human review is still needed.
Key: 🟢 = good. 🟠 = warning. 🔴 = attention required. 🔵 = info. ⚪ = unknown.}

^{For full details, please see workflow run 26501391203}

[lissy93]

For anyone looking for the en whitepaper: https://github.com/number571/hidden-lake/blob/master/docs/translated/en/hidden_lake_anonymous_network.pdf

This looks cool @number571 - thanks for the submission.

Security model looks solid, and nice and transparent docs. My initial thought is that this probably shouldn't be listed at least not in this section, it's a F2F network, so you're only going to be anonomized among a small group of users (more like 1 in 10 instead of 1 in a million).

[number571]

@lissy93 Good afternoon, the network is indeed F2F and is primarily limited to a small circle of users. However, with 8Kbps/5s bandwidth and a 100Mbps bandwidth limit, the network can handle up to 8,000 users. Depending on the adapters selected and the configured settings, this limit can be adjusted quite flexibly and reach tens of thousands of users. Based on the anonymization goal itself, it doesn't hide subscribers in a crowd, as Tor/I2P does, but rather conceals actions through the system itself, which sounds more like the cryptographers' lunch problem (DC networks). Therefore, the number of users is not fundamental to anonymity in theoretical terms. F2F connections are hidden within the overall system, so even if the number of friends is less than 10 and the total number of nodes is 1,000, it is impossible to detect the presence of a F2F connection. Thus, F2F is an add-on to the QB-problem and, in this case, it is more of an anonymous network than a communication platform like RetroShare.