Excited to try this out: https://github.com/roogle-dev/reticulum-phantom
> Decentralized, end-to-end encrypted P2P file sharing over the Reticulum mesh network. The first torrent-like application built natively on Reticulum.
Update: I was informed this was vibe coded and finally got around to reading more into it. I can't recommend this. Please see this link for more info: https://github.com/roogle-dev/reticulum-phantom/issues/3#issuecomment-4285042507

Decentralized, end-to-end encrypted P2P file sharing over the Reticulum mesh network. The first torrent-like application built natively on Reticulum. - roogle-dev/reticulum-phantom
@perlman Ok, to show I am not just talking either, here is a #reticulum protocol analysis with focus on #privacy
Including comparison to other projects.
The TLDR is: #RNS is reasonably good hiding identity from services, but leaks metadata on network level.
https://codeberg.org/MarSik/reticulum-audit/src/branch/main/reticulum-source-privacy-flaw.md
I tried to back up all my claims and reasoning with links and sources. But feel free to call me out on any inaccuracy as the final text is rather long and I might have missed something. #tor #i2p can check me too.
A NomadNet/RNS Transport for the South-East Asia region.
IPv4/IPv6
Propagation Node: 2ec4f625458c697d8fd65a8becb87a41
Nodes/clients in the region are welcome to add via TCP.
Connected nodes: 211
Backbone peers: 4
[[NomadNode SEAsia TCP]]
type = TCPClientInterface
enabled = yes
target_host = rns.jaykayenn.net
target_port = 4242
Contact: lxmf@01fc01580164cf4c7ea663ab98ba4209