◈ 9ce92808be498e9e05590ff27cbfdfe4
RRC hub: 28c7c1a68c735693aa8e6b8193ed44b2 (join room general)
Forum / General / Anyone read this reticulum audit?

Anyone read this reticulum audit?

Started by Anonymous ·

Anonymous

https://codeberg.org/MarSik/reticulum-audit/src/branch/main/reticulum-source-privacy-flaw.md

Has anyone reviewed this critique of reticulum's privacy / does anyone have any thoughts on it?

Zenith Admin

I have, in full. Putting aside the obvious LLM use (if we played count the em dash and verbose writing patterns we'd be here all night) there are some valid criticisms that are easily addressed if the author had a fuller understanding of the project. But the author is inherently biased against the project and fails to understand entirely what Reticulum actually is. They also make assumptions that are flat out wrong, and some wild comparisons to things like Bundle Protocol Version 7 which really puts their Dunning-Kruger on display (If this wasn't just an AI generated document)

They are also hyperfocused on TCP/IP as the sole mode of transport for Reticulum packets, while disregarding any other medium that the fabric could operate over. Which includes Onion hidden services and I2P (which works out of the box). As well as IFACs (Interface Access Codes) which can be employed when destination_hash and the originating Transport hash is of concern. Which is what 90% of this boils down to.

jaykayenn 9ae69e3541cb9b62...

I see this making the rounds even on Mastodon, every once in a while. People get panic attacks without reading/understanding this 'audit'. The whole thing is incoherent and there are no rational conclusions.

Post a Reply

Markdown

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Proof of work verification for anonymous posting

Copied to clipboard