Encrypted file storage, share links you actually set the rules on, or go P2P
Turn on encryption and your upload is scrambled client-side with AES-256-GCM before it leaves your browser. The key is generated server-side once, emailed to you, and never stored after that — lose the email and the files are gone too. There's no recovery flow, because building one would mean keeping a copy of the thing we're claiming not to keep. Share links with real rules Files you store sit…
To encrypt files for storage and sharing, a service enables client-side scrambling using AES-256-GCM before the upload leaves the user's browser. The unique encryption key is generated server-side, emailed to the user, and then permanently deleted, making recovery impossible if the email is lost. Share links come with independent password protection, download limits, and expiration dates, all of which can be individually modified or revoked. Two links to the same file can have entirely different rules.
The service supports real-time cursors and search functionality across notes, featuring default live cursors and seamless note search. Locking a specific note disables both cursor tracking and search capabilities, as neither can function without the server processing the note's contents. This feature is set per-note, rather than applying to the entire account.
Alternatively, users can establish connections directly between browsers using a six-digit WebRTC data channel over DTLS, bypassing the server entirely. This method allows for data transfer without any upload restrictions, size caps, or server involvement. The entire setup utilizes Next.js, a Laravel API, Postgres database, Reverb for live-cursor synchronization, Backblaze B2 for storage, and runs on a small Kubernetes VPS. The service is accessible at sharenod.com, and it is free to use.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
