Souspli

Souspli / Docs / Use

Sharing a letter

A letter is a file. Any way of moving a file moves a letter, and none of them can alter it: whoever receives it re-verifies everything.

Open a letter and press Share…. There are four ways out, in increasing order of how much they reveal.

1. Save as file

Save as file… writes a .thing file — an exact, byte-for-byte copy of the bundle as you hold it. Email it, put it on a USB stick, attach it to a chat. It keeps its author, its signature and its hash wherever it lands; saving someone else's letter does not re-sign it as yours.

Reveals: nothing, to anyone, beyond whatever channel you send the file through.

2. Copy bundle

Copy bundle puts the same bytes on your clipboard as text, for pasting into someone's Ingest box. Practical for small letters — a comment, a vote, a memo.

Reveals: nothing beyond the channel you paste into.

3. Seed over BitTorrent

Seed over BitTorrent serves the letter from your machine and gives you a magnet: link. Anyone who pastes that link into Ingest downloads it from you, or from anyone else seeding it. This is how large letters travel — an article with video, a photo set.

Reveals: your IP address to the BitTorrent DHT and to every peer, along with the fact that you hold this letter. A sealed letter stays encrypted; that you have it does not stay secret.

4. Post to relays

A relay is how a letter reaches someone who did not ask for it — which is what makes a public conversation possible. Souspli uses Nostr relays.

On the receiving side, letters posted to relays you subscribe to arrive in your feed after passing the same checks as any file. A pointer arrives as an offer: a row saying a letter exists, who offered it, and a Fetch button. Nothing is ever downloaded automatically — not a thumbnail, not a byte — until you press it.

Reveals: posting tells each relay your IP address, and tells the relay and all its readers that your key published this letter. Subscribing tells the relay what you are interested in. Your letters also declare your Nostr key, which is what lets readers confirm that the person who posted is the person who signed.

Getting a letter in

The Ingest box takes any of:

Paste What happens
a bundle as text Verified and added. Nothing touches the network.
bundle:<sha256> Looked up in your own store by exact content hash.
magnet:?xt=… Starts a background transfer. Shows ⚠ contacts the BitTorrent network first.
https://…/file.thing Downloads it. Shows ⚠ tells <host> your IP first. Provisional — may be removed.

A URL names a place, not content: admission proves that what arrived is a validly signed letter, not that it is the one you meant to fetch. Look at the author.

Private letters

A sealed letter is encrypted to each recipient, with the author's identity inside the ciphertext. Someone who gets the file without being a recipient can't tell who wrote it or who it's for. They can see only that it exists and roughly how big it is.

To write one, add people in the To row of New (or press Write privately… in People), then publish as usual. How to choose recipients is in People. If you have relays, the confirm offers to send it through them anonymously, and the box starts ticked. You can also send it later with Share → Send privately to relays. Or hand the file on the way you would any other: Share → Save as file or Copy bundle.

Sending privately reveals: each relay learns your IP address, the time, and that an encrypted letter of about this size was posted. It doesn't learn who wrote it or who it's for: it's posted under a key made for that one post, and the event names nothing else. Every reader's app receives it and tries to open it, and only the recipients can. A letter over 32 KiB can't go this way, and must travel as a file.

When you open one, it's decrypted into memory only. Nothing in the clear is written to disk. After a restart, Souspli decrypts it again from the sealed file it arrived in.