RFile

RFile documentation

DIFFERENT NETWORKS

Keep an authenticated RFile link across the internet.

Status: Preview

Internet pairing is a Preview capability. RFile exchanges a private one-time code, authenticates the other device, prefers a direct peer-to-peer path, and can use iroh relay connectivity when direct networking is unavailable.

Pair across networks

  1. Create a code

    One user creates a temporary internet-pairing code in RFile.

  2. Exchange privately

    Send the code through a private channel to the intended person.

  3. Connect and compare

    The other user enters the code. Both users compare the displayed confirmation before accepting.

  4. Keep both apps online

    Browsing and transfers require the participating RFile applications to remain available.

Google Drive’s connection entry, Nearby & background settings, and VLC plugin controls. Edited app-state walkthrough recorded in RFile 0.3.67; it does not show a completed pairing, signed-in account, shared-folder browsing, plugin removal, or live transfer.

Direct and relay routes

  • Direct P2P

    RFile prefers a direct authenticated transport path when both networks and endpoints permit it.

  • Iroh relay fallback

    When direct connectivity cannot be established, the encrypted transport can use an iroh relay path. Relay use changes the network route, not the device identity or granted file permissions.

Throughput and file count

RFile does not impose a marketing promise for internet transfer speed or a claim that every workload has no limit. Practical throughput depends on both internet connections, the selected route, relay conditions when used, storage, CPU, memory, and the file workload.

Large collections are transferred as bounded jobs. Protocol, memory, filesystem, service, and operating-system limits still apply even when the interface does not require one request per visible file.

Related documentation