maynet

Stirring in the network

Julian-X

18 Jun 2022

Have you ever seen a system get nervous? That’s what this feels like.

Maynet’s logs are jittery. Bursts where there should be flows. Empty space where there should be noise. It’s like the machine equivalent of pacing.

In Prague, drones circled the same block for hours, chasing nothing. In Paris, data relays looped packets until they burned out. In Stockholm, watchers moved in groups, then vanished into the night.

Something’s rattled them. I’m not saying what, because I don’t have to. You feel it too. The system knows it was touched, even if it can’t prove where.

Take the nervousness as a sign. We’ve done something. And Maynet knows.

Mission brief: building distributed communication

The mission on September 9–10 is clear: we will design and prototype a distributed communication system for the Rebels. This system must allow one-to-one and group conversations without relying on a central server or service. Messages must pass directly between participants, making manipulation by Maynet impossible. The goal is

Mission guidelines: environments and tools

With the mission less than a week away, we confirm the technical requirements for all participants. These are not suggestions. They are rules. Maynet thrives in careless environments; we will not give it an opening. Operating systems * Linux remains the primary recommendation. * MacOS or Windows may be used only if

Recommendations repeated

For those at the back of the class: here are the rules, again. * Use Linux. Prefer European distributions. * Trust open source. * Avoid .NET, React, TypeScript. * Never use AI online. If you must, run it local, offline, and air-gapped if possible. * Communication? Radio is safe from manipulation, but open to listening.

Mission secrecy

The Rebels confirm that details of the September mission will not be shared until the beginning of the month. This is intentional. Channels cannot be trusted. Manipulated words could collapse plans. The less we write, the less Maynet can twist. [2025-08-17 22:55] mission_plan.log Date: September 9–10

Read more

Mission brief: building distributed communication

Mission guidelines: environments and tools

Recommendations repeated

Mission secrecy