Без интернета на другой конец света

Main technological concept

• Reticulum is presented as an independent network stack for private messaging that can work without Internet.
• It uses a decentralized, multi-hop mesh-style architecture, allowing messages to be routed through intermediate nodes.
• It is described as serverless—with no central server and no IP addressing—making it difficult to “isolate” or shut down in the usual way.

Claims about connectivity & routing (product/architecture behavior)

Automatic fallback across transport layers

• If home/mobile Internet fails, it switches to local Wi‑Fi.
• If Wi‑Fi isn’t available, it switches to Bluetooth to nearby devices.
• It can operate even when there are few networks/radio signals, by finding workable routes via nodes.

Dynamic multi-hop delivery

• Messages are forwarded through relay nodes, with an example chain such as:
  • phone → Bluetooth pocket node → radio repeater node(s) within ~20 km → bridge node → Internet “last mile”
• The network is described as supporting up to 128 stable hops.
  • The narration compares this to:
    • “mice” having 7 hops
    • Internet often using fewer than 20 hops for global routing
• If a node drops out, the network rebuilds routes to bypass it (dynamic pathfinding).

Privacy & security features emphasized

• End-to-end encryption

  • Data is encrypted on the sender device using the recipient’s keys.
  • Intermediate nodes act as “blind couriers,” described as seeing only a hash address of the next hop (not the sender’s real identity/location).

• No third-party server storage

  • The chat is described as remaining “exclusively yours,” not being sent to third-party servers.

• Metadata interception claim

  • Because of the architecture (“no IP addresses / no central point”), the narration claims interception becomes “mathematically useless,” and only the sender and recipient can read messages.

App / tutorial: how to install and start using it

Where to download the messaging client

• The messaging client is referred to as “Messenger Side Band” / “SйБН app” in the subtitles.
• It is not available on Google Play.
• Users are instructed to download it from:
  • the official Reticulum website, or
  • Mark Qvist’s website
• Platforms mentioned: Linux, Windows, Mac, Android.

Installation workflow (Android-focused)

• Download from an official GitHub repository (select the correct file, e.g., APK).
• After installation, the app is described as being checked by security tests.
• The tutorial instructs users to improve security by removing “browser permission to install packages” via:
  • Android Special Access → External Sources.

Contact / identity model

• No phone/email/IP/nickname-based accounts.
• Users exchange regenerated hash addresses (LXMF address).
• The LXMF address is shown in the app under:
  • Preferences → address and Identity

Connectivity settings in the app

• Enable transfers via Wi‑Fi / Ethernet / TCP and Airod(e) (as stated).

How to start chatting

• Use Send announce to broadcast the address to a feed.
• The recipient checks the Stream list, then uses Converse from the address entry.

Message types supported

• Text
• Voice messages
  • low/high quality
  • described as packetized sending (example: push-to-talk-like behavior)
• Images
  • low/medium/high
• Files

Tutorial: communication without Internet using a “node” device

When a node is required

• If there’s no Internet (or the other side has no Internet), you need a radio node to provide messaging (sound/files/text).

Node setup (described)

• In the RNE tab:
  • set radio frequency (example: 433 MHz)
• Enable four switches (per the subtitle instructions).

Bluetooth pairing between phone and node

• Turn on Bluetooth on the phone.
• On the node:
  • press and hold the left button ~10 seconds to generate a code.
• In the app:
  • Connect and enter the code.
• After pairing:
  • the Reticulum logo appears
  • messaging can proceed “via radio.”

Automatic path choice described

• When the node is on: communication uses radio.
• When the node is off: the app uses Wi‑Fi or mobile network automatically without extra messenger settings (as described in the narration).

Tutorial: building / firmware-flashing your own node (hardware example)

Hardware example: HTG board

• Connect an antenna (warning: without it the board may burn out).
• Connect to a PC via a data cable.

Driver steps

• Check Device Manager; install/update the driver.
• Download the driver from Silicon Labs (“universal driver”).

Firmware flashing workflow

• Use an online software update tool created by AML.

• Steps:

  1. Select board type and frequency
  2. Choose the firmware file
  3. Click Flash
  4. Select the correct port
  5. Wait for flashing
  6. Initialize the device
  7. Install a firmware hash (last step)

• Follow-up video is mentioned:

  • stable connection 10–20 km (urban/open areas)
  • best frequencies, antennas, boards, and optimal configuration

End-to-end takeaway (as stated)

• Reticulum is positioned as a way to achieve guaranteed private communication when other civilian technologies fail (“turn into pumpkins”), suitable for:
  • text
  • short voice
  • files
• The narration adds that it offers “sufficient speed” for these use cases.

Main speakers / sources (from the subtitles)

• The video narrator/host (speaks throughout; includes “let’s go,” “I’ll show you,” “I’ll make a separate video”)
• Mark Qvist (named as a source for the app download site)
• Silicon Labs (driver download source)
• AML (source of the online firmware update tool)
• Liam (credited in the firmware/app tooling context, per subtitle)