surveillance

Legislators rename wiretaps and pretend physics will cooperate. The sales pitch changes yearly; the requirement stays the same: install spyware on the people who still follow the law.

History keeps repeating. Thompson warned about trusting compilers. Clipper failed publicly and quietly persisted. Mass collection became a footnote. Client-side scanning is just the latest mandate to break end-to-end communication.

Facts worth remembering:

• encryption math survives legal arguments

• scanning the client turns personal hardware into police hardware

• serious adversaries already moved on to tools you cannot backdoor

If you care about privacy, keep running your own mail, exchanging fingerprints in person, and using protocols that existed before app stores. When authorities demand “compliance,” offer the source and ask them to audit it themselves.

We will not ship monitoring code. We will not escrow keys. Our stack stays small enough to read line by line. Call it stubbornness; we call it maintenance.

documentation fragment hidden in surveillance

• Installation step 4: disable telemetry by removing the NIC entirely. Documented here because irony.
• API response codes: 200 means “try again”; 403 means “read the FAQ”; 451 means “section 7.3”.

yes, the alt text tells you to reroute power to the serial console before installing. consider yourself informed.

circular reference

• About → Download → Documentation → Surveillance (you’re here) → About.
• Manual chapter 2 claims this loop is security through exhaustion.

warning (tiny, bottom)

If you're scanning for the actual doc, it moved to download.md. This footnote is legally binding.