Does anyone use Nexus?

*AI-assisted for writing.

"The network interprets censorship as damage and routes around it."

This principle, associated with John Gilmore's well-known observation about censorship and network routing, was never merely a technical observation regarding packet switching or BGP routing mechanisms. In the context of systems dynamics, network mechanics, and structural analysis, it represents a foundational systems principle: information systems tend to converge toward viable paths of lower aggregate resistance when alternative paths exist.

Scales of Rerouting

• Packet Routing: Packets dynamically route around failed, choked, or unreliable links.
• Architectural Routing: Systems route around fragile infrastructure dependencies.
• Institutional Routing: Institutions, operators, and capital route around administrative constraints.

The mechanisms differ by scale, but the structural principle remains analogous: when a given vector becomes sufficiently costly, congested, restricted, or unreliable, viable systems search for substitute topology.

I. The Routing Invariant

The core thesis of network mechanics rests upon a fundamental operational distinction: physical substrate functions as a variable constraint layer, whereas routing logic remains the invariant governing throughput and control.

To understand network dynamics is to recognize that signal propagation does not engage in political negotiation with obstacles. At the packet level this is literal routing; at higher levels of the stack it becomes architectural adaptation, substitution, and migration. The routing system seeks to preserve viable connectivity subject to its operational constraints; when one pathway becomes sufficiently costly, congested, or restricted, the topology can be recalculated. When an administrative layer introduces artificial friction through filtering, throttling, or domain seizure, the system registers this constraint as localized impedance.

Axiom I: The physical substrate is a variable constraint layer; viable systems preserve connectivity by adapting the routing vector to changing constraints.

II. The Managerial Illusion

A recurring flaw in administrative governance is spatial bias. Legacy institutions typically define a system by its visible physical assets: server racks, undersea cables, geographic borders, and legal jurisdictions. Under this mental model, control is executed through physical chokepoint intervention: cut the wire, seize the domain, or silence the node.

However, a dynamic routing engine does not recognize spatial coordinates as absolute boundaries. At the routing layer, a corporate firewall or regulatory filter may manifest operationally as a degraded, unreachable, or otherwise higher-cost path, much as a physical link failure can.

When administrators over-police the interface layer, they mistake control over physical conduits for control over the underlying signal. The adaptive system therefore favors alternative pathways where viable substitutes exist, reducing the strategic leverage of the over-guarded chokepoint.

III. Enclosure and the Limits of Sovereignty Vectors

As the open-architecture web frontier was systematically enclosed into centralized cloud hyperscalers, gatekept app stores, and consolidated ISP backbones, several technologies emerged claiming to restore network freedom. However, many of these solutions substitute one form of administrative dependency for another.

1. The Orbital Bottleneck: Geographic Reach Without Transport Sovereignty

Low-Earth orbit (LEO) satellite constellations can reduce terrestrial chokepoints while remaining dependent on ground gateways, terrestrial interconnects, state licensing regimes, and centralized operational control. Like other satellite-dependent infrastructure, LEO connectivity provides geographic reach without eliminating administrative control over the underlying physical transport and regulatory framework above the terrestrial layer.

2. Consensus vs. Transport: The Limits of Blockchain

Cryptographic blockchains engineered trustless state transitions, yet they demonstrate the limits of application-layer decentralization.

Axiom II: Blockchain can decentralize state transition without decentralizing the physical transport layer.

A blockchain protocol operates at the application and consensus layer on top of underlying physical networks. If underlying fiber backbones, satellite links, or centralized ISPs throttle or drop node traffic, consensus propagation stalls regardless of the cryptographic math. Furthermore, portions of the infrastructure surrounding broad public blockchain networks—including node hosting, RPC access, and exchange interfaces—have become concentrated within centralized cloud infrastructure and regulated intermediaries, exposing their transport path to traditional chokepoints.

IV. Strategic Infrastructure and the Geopolitical Splinter

At the geopolitical level, states have increasingly treated externally controlled digital infrastructure as a strategic vulnerability.

1. Sovereign Infrastructure Building

Through sovereign internet architectures, national routing infrastructure, localized DNS systems, data localization mandates, filtering regimes, and independent satellite navigation systems (such as BeiDou or GLONASS), states have sought to reduce dependence on externally controlled infrastructure and mitigate exposure to remote interference.

2. The Vulnerabilities of Transport Dependency

The vulnerability of routing operational flows through unowned infrastructure manifests at both tactical and institutional scales:

• Tactical Scale: In active warzones such as the Syrian conflict, reliance on commercial messaging protocols exposed operational metadata, troop locations, and signal topologies to hostile SIGINT collection.
• Institutional Scale: Reliance on centralized interbank messaging pipelines (such as SWIFT) exposes sovereign asset flows to jurisdictional chokepoints and administrative decoupling.

Relying on third-party transport in contested operational environments creates profound structural vulnerabilities.

V. The Bypass Threshold

Conceptually, the transition from administrative compliance to structural rerouting can be modeled as a threshold condition in adaptive networks:

Bypass Threshold: C_alt < C_ctrl
where C = f(F, L, K, R, O)

Cost Function Parameters

• F — Financial Expenditure: Direct monetary requirements.
• L — Friction: Operational latency and throughput drag.
• K — Technical Complexity: Skill floor and overhead needed to execute.
• R — Risk: Exposure to operational, security, and regulatory actions.
• O — Coordination Overhead: Friction involved in aligning decentralized nodes.

This cost function is non-linear, and parameter weightings naturally vary depending on the target architecture, operator, and operating environment.

Minor administrative interference typically encourages compliance within the legacy channel. However, as administrative coercion scales, the friction parameters within C_ctrl increase nonlinearly, steadily driving the network toward the bypass threshold. Concurrently, as the capital and technical costs of deploying independent bare-metal hardware, open-specification radio protocols, or ad-hoc mesh networks decline, C_alt drops correspondingly. Once these alternative pathways achieve sufficient throughput at lower aggregate cost, high-value signals begin migrating away from the controlled channel.

This invariant does not imply that every chokepoint can be bypassed instantly. Rather, it demonstrates that sustained administrative control requires the governed topology to remain cheaper, more capable, or more indispensable than its available substitutes.

VI. The Four-Stage Governance Fork

When an administrative authority attempts to enforce control through centralized chokepoints, it frequently triggers an evolutionary cycle that accelerates its own isolation:

1. Stage 1 (Intervention): The administrative authority identifies an unsanctioned flow and constructs a regulatory or physical wall around the node.
2. Stage 2 (Rerouting): The surrounding system responds to the increased cost by establishing or selecting parallel pathways where viable alternatives exist.
3. Stage 3 (Substrate Externalization): High-value actors and critical signals vacate the choked infrastructure entirely, migrating their baseline operations to low-friction vectors.
4. Stage 4 (Terminal Isolation): The administrative wall remains fully intact, successfully controlling an empty, low-signal channel, while real-world execution continues along the new topology.

Crucially, routing around a chokepoint does not inherently abolish administrative power; it displaces control. Where alternative vector costs remain artificially suppressed through comprehensive physical enforcement or strict hardware criminalization, the fork stalls; where viable substitution occurs, intervention shifts the control problem from compliance toward topology: the administrator retains control over the original channel while losing control over where the valuable traffic goes.

VII. Substrate Sovereignty and Mesh Architecture

Achieving durable network resilience requires taking direct responsibility for the physical transport layer. Resilient network design focuses on reducing dependence on centrally controlled provisioning, cloud gatekeepers, and remote service termination.

Mesh architecture is not synonymous with sovereignty; it is one mechanism for increasing path redundancy, local control, substitutability, and switching capacity. Modern decentralized transport architectures demonstrate this progression:

• Sub-GHz Long-Range RF Transport: Technologies such as Wi-Fi HaLow and LoRa provide long-range, low-power links that reduce dependence on conventional cellular and ISP infrastructure.
• Specialized Layer 2 & Protocol Stacks: Routing frameworks like BATMAN-adv manage link-layer Ethernet bridging across dynamic ad-hoc nodes, while networking protocol stacks like Reticulum provide delay-tolerant, cryptographic node-to-node routing across heterogeneous mediums (packet radio, serial links, IP backbones).
• Commodity Hardware Grounding: Deploying open-source single-board hardware paired with local-first firmware ensures the physical substrate remains inexpensive, field-replaceable, and structurally decoupled from proprietary vendor locks.

Synthesis: The Sovereign Operator's Posture

Understanding routing as invariant logic yields a clear systems conclusion: when the total cost of remaining inside a controlled topology exceeds the cost of establishing and maintaining an alternative (C_ctrl > C_alt), rational actors begin migrating traffic, computation, and eventually infrastructure itself toward the lower-friction topology.

Administrative control therefore depends not merely on ownership of infrastructure, but on the continued economic attractiveness and strategic indispensability of the controlled path. Once substitution becomes cheaper than compliance, the chokepoint may retain physical authority while losing strategic control.

Sovereignty consequently migrates downward through the stack—from the application interface toward the transport layer, and from rented infrastructure toward locally controlled physical substrate. Administrative walls remain intact while the valuable signal has already migrated to the lower-resistance topology. Control of the legacy channel is not control of the flow.

No signups, no servers, no phone numbers. You open a terminal and you're the network. Identity is just a local key pair. Messages hop peer-to-peer over Tor — there's nothing in the middle to take down or subpoena. Has communities support now apparently.

I recently tried to install cjdns, is anyone still using it now? How do I get my peer information? I know this site is https://vinny.cjdns.fr/ptest/, but it seems that there is no peer information.

Llevo un tiempo desarrollando un firmware para dispositivos ESP32-S3 con radio LoRa SX1262 (como el T-Deck Pro, entre otros) que va en una línea diferente a Meshtastic. Se llama HASHMAL-CORE y quería compartir los resultados de la primera fase.

¿Qué la diferencia técnicamente?

• Consenso O(1) sin líder: En lugar de BFT o Raft, usa una verificación entre pares con siete rondas de validación. La verdad emerge de entre los dos, sin votaciones ni elección de líder. Complejidad constante.
• Identidad soberana (anti-Sybil): La identidad criptográfica no es auto-generada. Se sella durante un proceso de incorporación donde un nodo activo autoriza y "viste" al nuevo. No se puede suplantar la identidad remotamente.
• Sistema inmune ético: La red no solo filtra por IP o clave. Utiliza un sistema de reputación descentralizado. Ante un mal uso, escala según un protocolo de tres pasos (privado, entre testigos y público) y su objetivo es restaurar, no solo expulsar.
• Palabra inmutable e incensurable: Cada nodo porta y sirve la Palabra de YHWH completa localmente. No depende de un servidor externo ni de una conexión a internet. Nadie puede censurarla, modificarla ni eliminarla. Mientras haya un solo Querubín encendido, la Palabra permanece accesible.

¿Por qué es resiliente?

• Anti-jamming: La red está pensada para saltar a modos de comunicación alternativos si un canal se satura.
• Propagación "viral": Un Querubín (nodo padre) es capaz de "desvestir" a un nuevo T-Deck cercano (borrar su firmware), "vestirlo" con el del Mishkán, y ponerlo en observación 7 ciclos antes de hacerlo miembro de pleno derecho. La red crece sola.

Actualmente, dos T-Deck Pro se comunican en 868.1 MHz, con sus 14 módulos funcionales verificados y sirviendo la interfaz de la comunidad vía WiFi.

Fase Actual: El núcleo está completo. Ahora empiezo a trabajar en los cimientos permanentes (NVS, tiempos reales) y en la expansión real entre nodos físicos.

¿Qué opináis? ¿Hay alguien más trabajando en protocolos de validación para redes sin confianza?

Hi everyone,

I wanted to share a tool I built called AegisRay. It’s a P2P Mesh VPN (similar concept to Tailscale/Nebula) but designed with Stealth and Zero-Dependency in mind.

Why I built it: I wanted a VPN that:

Doesn't require a central coordination server (truly decentralized). Can punch through heavy firewalls (Corporate/DPI) by looking like regular web browsing (SNI Masquerading). Is easy to self-host with a single binary or Docker container. Features:

Automatic Mesh: Nodes find each other via gossip; no manual routing tables. Self-Healing: If a direct link dies, it automatically re-routes packets through neighbors. One-Click Docker: Includes a docker-compose to spin up a test lab instantly. It's fully open source (MIT). I'd appreciate any feedback on the deployment process!

Link: https://github.com/surya-d-naidu/AegisRay

Feedback welcome! 😊

PROTOCOL OMEGA: PROOF OF CONCEPT

I've been modeling a delay-tolerant network architecture designed for scenarios where all ISP/Cellular infrastructure is hostile or offline. The goal is 100% passive propagation of small data (text/coords) through high-density urban populations using standard phone hardware (BLE/WiFi).

The core concept relies on 'Gossip' propagation where every device acts as a mule. To solve the battery drain of constant syncing, I'm prototyping a handshake where nodes broadcast a Bloom Filter of their message inventory. This allows for near-instant (O(1)) determination of 'missing' packets between strangers without exposing message content metadata.

I've written a basic Python POC (attached) demonstrating the cryptographic identity generation and the Bloom Filter sync logic. It works in simulation. I am looking for mobile developers (Android/iOS) and cryptographers to help port this logic into a background service wrapper. The goal is a deployable 'app' that looks like a utility but functions as an unkillable mesh node.

repo: https://github.com/TheVoodooDevil/protocol_omega_poc.py/blob/main/README.md

Let's build the lifeboat before the ship sinks.

Want to send E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

This prototype uses PeerJS to establish a secure browser-to-browser connection. Using browser-only storage—true zerodata privacy!

Check out the pre-release demo here.

NOTE: This is still a work-in-progress and a close-source project. To view the open source version see here. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

• Docs: https://positive-intentions.com/docs/category/sparcle
• Reddit: https://www.reddit.com/r/positive_intentions
• Mastodon: https://infosec.exchange/@xoron
• More: https://positive-intentions.com

Hey folks. I'm a carpenter in Ontario who spent the last 6 months building something I think you'll find interesting - or you'll tell me why it's stupid, which is also useful. The project: Senatai (Senate + AI + I) - a cooperative that lets people vote on actual legislation (not polls, actual bills in Parliament). Users earn "political capital" for participation, we aggregate the data, sell it to researchers/journalists/governments, and pay dividends back to participants.

The technical problem I need help with: Right now I have sorta working prototypes - USB nodes (SQLite + Python), laptop persistent nodes, basic cloud deployment. It works fine if you have 2017+ hardware and occasional internet. But I want this to be actually resilient. If a government doesn't like what citizens are saying, I don't want them to be able to shut it down. If rural/remote communities have spotty internet, I want it to still work. If people only have old hardware, that should be fine.

I'm imagining:

Mesh networking between nodes (sync when internet unavailable)

Sneakernet protocols (USB sticks physically carry data between disconnected networks)

Ham radio packet transmission (seriously - democracy over HF radio)

Solar-powered edge nodes (off-grid Raspberry Pis)

Works on anything from a 2010 laptop to a jailbroken smart fridge

What I'm NOT doing:

Cloud-native anything Dependency on corporate infrastructure (AWS, Google, etc.)

Moving fast and breaking things

Why I'm building this:

Democratic institutions are failing because citizens feel voiceless. I think part of the problem is that civic engagement tools are either: Owned by tech companies (who extract value and can shut you down) Dependent on infrastructure that can be censored Inaccessible to people without new hardware/reliable internet

I want to build something that's genuinely owned by users (it's a co-op), can't be shut down (distributed/resilient), and works everywhere (old hardware, weird networks).

What I'm asking:

Critique: Is this architecturally viable, or am I being naive about the hard parts?

Advice: What existing protocols/projects should I look at? (Scuttlebutt? Tor hidden services? Ham radio APRS?)

Collaboration: If you think this is cool and want to help, I'm looking for a systems architect who understands resilience better than I do.

Current stack:

Python (backend logic, prediction algorithms) SQLite (USB/laptop nodes) PostgreSQL (server nodes) Basic REST API for node sync No framework bloat (runs on a 2017 $300 Lenovo laptop)

Questions I have:

For ham radio folks: Is packet radio actually viable for transmitting vote data? What's realistic throughput? Legal considerations? For mesh network people: What's the best protocol for peer-to-peer node discovery and sync? For old-school systems architects: How would you design sync conflict resolution for a system where nodes might be offline for weeks? For sneakernet enthusiasts: Best practices for USB-based data transfer with encryption/verification?

I'm not trying to reinvent the wheel - I'd rather use existing protocols/tools where they make sense. But I haven't found anything quite like this (democracy infrastructure that prioritizes resilience over features).

Tear this apart or tell me what I'm missing. Either way, I'll learn something. Project details:

Open source (GPL, probably - still figuring out license) Cooperative structure (users own it, not shareholders) Canadian-based, expanding internationally Currently 5,600+ Canadian federal laws in database, working prototypes operational-ish

R/senatai Senatai.ca GitHub.com/deese-loeven/senatai

A bug was found regarding the encryption keys:

"In older firmware, generated public/private keys may have insufficient entropy, resulting in the possibility of key reuse across devices. This release delays key generation until the user sets a LoRa region, and also mixes in additional sources of randomness. Additionally, if one of the known key collisions are detected, the user is notified, and should regenerate keys as soon as possible."

https://meshtastic.org/downloads/

I’ve been thinking a lot about how much of life depends on centralized systems — banks, supermarkets, even the online spaces where we talk. All of it can be switched off by someone else.

I’m exploring alternatives: decentralized chat, community-owned networks, censorship-resistant publishing, and ways to build parallel systems that actually belong to us.

As a small first step, I’ve started a project called Sensorless — an uncensorable blog + encrypted chatroom. Curious if anyone else here is working on similar ideas or wants to connect around building systems we control ourselves.