FEATURE GUIDE
Send files without cloud storage
Orylin sends encrypted chunks in the active browser session, verifies the received bytes and keeps no cloud archive.
Chunk, encrypt and verify
The sender divides a file into bounded chunks, protects application records with the active session keys and streams them over the selected browser path.
The receiver updates a SHA-256 digest while bytes arrive and compares the final result with the announced digest. A completed UI state is based on verified bytes, not only on a successful network request.
Limits follow the active path
Direct WebRTC is the preferred file path. A user-enabled volunteer relay can carry files up to the current 2 MiB relay limit while forwarding only ciphertext.
The public Nostr rescue path does not support files. When a session uses that path, file sending is disabled and the reason is shown.
Save files in the browser or to disk
In compatible Chromium browsers, a recipient may choose a destination so larger Direct transfers can stream to the selected file handle. Otherwise the implementation uses a bounded browser-memory budget.
Orylin does not keep a server-side copy for later download. Recipients still need to scan and evaluate files: encryption and transfer integrity do not establish that the sender or file is safe.