FEATURE GUIDE
File transfer without a cloud file locker
Orylin sends encrypted file chunks within the active browser session and verifies the received bytes progressively; it does not create a cloud file 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 should follow verified bytes, not merely 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. If the session falls back to that path, the interface must disable file sending and explain why.
Delivery and browser memory
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 should still scan and evaluate files because encryption and transfer integrity do not establish that the sender or file is safe.