> /home/jd

Peer-to-Peer Vault Mobile Synchronization Setup

Establish peer-to-peer synchronization of low latency between main workstations and mobile devices.

Purpose

đź”™ Main Context: This guide is part of the extensive architecture detailed in the Infrastructure MOC.

Establish a Peer-to-Peer (P2P) synchronization tunnel with low latency between the main workstation and mobile devices. This configuration forms the “Living Layer” of the 3-2-2 infrastructure architecture, allowing notes created on the desktop to appear instantly on the tablet, and vice versa, without relying on Dropbox cloud synchronization times.

Key Strategy: Isolate synchronization. Instead of synchronizing the entire 5GB Dropbox files to the mobile device, only the specific Obsidian vault folder (~50MB) is sent. This ensures a super lightweight mobile environment that doesn’t drain the battery or saturate the touch storage.

Step-by-Step Configuration (Hackintosh → Android)

Phase 1: Handshake (Device Binding)

So that devices can share encrypted information, they must first recognize each other mutually.

  1. On the origin machine (Hackintosh): Open the Syncthing web interface. Go to ⚙️ Actions > Show ID to reveal the device’s QR code.
  2. On the target device (Android Tablet - Syncthing-Fork App): Go to the Devices tab, press +, and use the camera scanner to read the QR code from the monitor. Assign an identifying name (e.g., “Main-Hackintosh”).
  3. Approval: On the Hackintosh, a notification for incoming request will appear. Click on Add device and save.

Phase 2: The Asymmetric Offering and Versioning

You must declare which folder will travel through the tunnel and how data will be protected against accidental deletions from the touchscreen screen.

  1. In the Hackintosh, click on + Add folder.
  2. General Tab: Assign a clear label (Boveda-Obsidian) and set the exact local path (e.g., ~/Dropbox/Obsidian/my-bodega).
  3. Share Tab: Check the box of the target device (Tablet-SM-P613).
  4. File Versioning Tab (The Vault): * On Hackintosh (Strong Server): Configure Simple File Versioning and retain 5 versions. This creates a hidden local security network (.stversions) in case something is deleted from the tablet.
    • On the Tablet (Lightweight Client): You must force No Versioning (No Versioning) to prevent accumulating junk files in the Android storage.

Phase 3: Landing on Android

  1. Upon receiving the shared folder notification on Android, open the request.
  2. Click on the gear icon ⚙️ next to Directory.
  3. Use the native Android explorer to create a clean destination folder (e.g. Documents/Safe) and select it.
  4. Accept the creation. The first synchronization of the megabytes will begin immediately.

Alert: Sync Error at 99%

The Symptom: The origin machine’s interface marks a small file (e.g., 7 bytes) stuck at 99% and the global state never passes to “Updated”.

The Diagnosis: Upon reviewing the logs of “Unsynchronized Elements”, a clash between file name rules was detected, between UNIX and Android. macOS allows the use of double quotes (") in note names, but the Android file system strictly prohibits certain special characters (", :, *, ?, <, >, |).

Example of conflicting files detected:

  • 03_Investigacion_"Autopsia_de_un_Sistema".md

The Solution: Rename notes from the original device (Hackintosh) to eliminate illegal characters (replace double quotes with single quotes ' or underscores _). Once renamed, Syncthing automatically propagates the change and the network status changes to 100% green (“Updated”).

Note of Expansion: This same P2P logic will be used in the future to connect the cellular phone and automate transfers of key photos or documents to the base station.

Automated translation (technical mode).

Enlarged view