Send Nearby
What it is
Hand a file straight to another NanumOS computer or a phone on the same Wi-Fi (the same router). It is like handing someone a sheet of paper: nothing goes through our servers or the internet, only inside the same home or office. The receiver always sees what is coming and how big it is first, and must press [Accept]. Received files go only into Downloads.
What to do now: turn receiving on (10 minutes) on the receiving computer, then pick that device on the sending one.
How to use it
Between NanumOS computers
- Receiver:
nearby onin the Terminal — receiving from everyone for 10 minutes, then it turns itself off. - Sender:
nearby scanfinds devices that are receiving;nearby send DEVICE FILE-OR-FOLDER…(up to four, folders included). - Both screens show the same six digits. If they match, the receiver types
nearby accept N, otherwisenearby reject N. - The sender shows progress every 10%; the files land in the receiver's Downloads under the same names ("name 2.txt" when a name is taken).
To a phone or any browser (send by QR)
nearby qr send FILE— a QR code and a short address appear.- Point a phone on the same Wi-Fi at it and open the page: there is a Download button. A folder or several files come as one zip.
- The link ends after one download, and after 10 minutes anyway.
From a phone to NanumOS (receive by QR)
nearby qr recv— a QR code; on the phone it opens a "choose files · send" page.- After the phone sends, NanumOS shows the name and size first; only
nearby accept Nputs it into Downloads.
With a Mac or Linux computer
Nothing to install: open the same QR address in that computer's browser (as above). NanumOS never connects to that computer first — it is always the other side that opens the link.
Settings
nearby— the state now (this device's name, receiving off/on, time left).nearby name NAME— the name other devices see (the computer's name by default).nearby mode known— always waiting, but only for devices you accepted from before; every transfer still needs [Accept].nearby mode offis the default.nearby off— off at once.nearby qr stop— end every QR link.
Not there yet: the desktop screens (Files' "Send Nearby…", the accept card, Settings › Sharing) and asking the assistant are the next version. Sending to your own devices on another network (through Wire) is next too. A broken transfer starts again from the beginning (no resume).
Technical details
- Sending: TCP 47761. Fresh X25519 keys every time; HKDF-SHA256 gives one key per direction and the six digits (equal on both screens = nobody in the middle). Everything travels in ChaCha20-Poly1305 sealed 32 KiB frames; each file's SHA-256 is checked at its end. Any mismatch removes everything received.
- QR: HTTP 47762, a 10-letter one-time token (base32), 10 minutes. A wrong or ended token is 403; 8 wrong tokens from one address = 429 for a minute. An upload whose Content-Length exceeds the free room is 413.
- Only private source addresses (10/8, 172.16/12, 192.168/16, 169.254/16, 100.64/10). Incoming names keep only their last part, with
..,/and control bytes filtered, so nothing can land outside Downloads. - Log: names, sizes and addresses in
/var/log/messages, never contents. Up to 256 MiB a file (the RAM file limit). - Contract
docs/contracts/NEARBY.md; teststests/nearby.py(two guest VMs),tests/test_nearby_core.py.
NanumOS 0.1.8349 · 2026-11-16