From folder to verified delivery.
Five steps. No central server in the middle. The recipient's machine and your machine are the only places the plaintext exists.
Publisher
Pick a folder. Click Publish.
Encrypt
AES-256-GCM, locally, per chunk.
NNTP Upload
Striped across your Usenet provider.
Share URI
A single link carries the pointer + key.
Consumer
Paste link. App reassembles & verifies.
Publisher selects a folder
You point Usenet Share at a directory. It walks the tree, captures unicode names, symlinks, hardlinks, and boundary-size files exactly as they are.
Files are encrypted locally
AES-256-GCM, per chunk, with keys generated on your machine. The plaintext never leaves. Your Usenet provider sees random bytes.
Chunks are uploaded over NNTP
60 concurrent connections to your Usenet provider. Redundancy posted alongside. Resume-safe if your connection drops or the app crashes.
You get a tiny share URI
A single link carries the pointer and the decryption key. Send it however you want — email, Signal, paper. The link is the whole share.
Recipient pastes the link
The app downloads, decrypts, verifies SHA-256 per file, and reconstructs the folder byte-for-byte. They never touch an NZB file or a par2.
The share URI
A single link is the whole share.
usenet://8fb92a@alt.binaries.data/71029#k=4f82a1c9e823b10Pointer + group + article ID + decryption key. Compact enough to text, durable as long as your Usenet provider retains the article (typically 4000+ days).
You need your own Usenet provider account.
Usenet Share doesn't include or resell provider bandwidth. We recommend Newshosting or Tweaknews — about $10–15/month for unlimited. Your bandwidth, your account, your relationship.
Read the full FAQ →