Souspli

Souspli / Docs / Use

People, vouches and your tribe

Souspli has no usernames, no follower counts and no reputation score. It has keys, and three ways of attaching meaning to them — each deliberately different.

File → People… lists every key whose letters you hold, with the name each one gave itself, in quotes, if it has signed a nametag or card. That name is their own claim. Anyone can pick any name, so it never replaces yours for them.

Finding someone

The find box above the feed takes either of these:

Names from other people are claims, so matching one doesn't prove the letter is from who you meant. The key is beside every row. To be sure, search by key.

The letter count beside each person in People is a link. Press it to fill the find box with that person's full address and see everything you hold from them.

To you, beside All, Mine and Replies, lists letters addressed to you and none you wrote: private letters you can open, plus public ones that name your key (a vouch about you, a contract you're asked to sign, a group that lists you).

Writing privately

A private letter is sealed: encrypted so only the people you send it to, and you, can open it. To write one, use the To row in New, or press Write privately… beside someone in People.

You can name a recipient in three ways:

Before you seal, Souspli shows who it's for and says plainly: anyone you send this to can forward it, with your signature intact. A seal keeps a letter from people it was never sent to. It can't stop a recipient from passing it on. There's no "recipients only" and no un-sending.

The list of recipients isn't written anywhere in the letter. A recipient learns that they could open it, and nothing more about who else could.

Until you send it, a private draft is saved on this computer unencrypted, like every draft. The header says so. Sending seals it and removes the draft.

To answer a private letter, press Reply privately. The reply is sealed to its author, and to you. A public comment would show everyone which letter it answers, and that you had received it.

Petnames: private

A petname is what you call a key: "Ada", "the ops account", "landlord". It is stored only on your machine, never enters a letter, and nobody else ever sees it.

That is exactly what makes it worth something. A letter can claim any name for its author; a petname is the one name nobody else can influence. In the header it is shown without a ✓, because it is your label and not a verified fact — and the key's address stays visible beside it, so the name labels the fact rather than replacing it.

Naming someone records that you recognise a key, and nothing more.

Vouches: public

A vouch is a signed letter saying I know this key — who they are to you, and optionally how you checked. Press Vouch… on a person.

Two things the app tells you before you publish one, because they are true:

A vouch says you recognise a key. It does not say they are honest, that they are who they claim to be, or that anything they signed is true.

Petnames are private; vouches are public. That is the whole difference, and it is deliberate.

Your tribe

Vouches are free to manufacture. Anyone can mint a thousand keys and have them vouch for each other in a circle, so counting vouches proves nothing.

What cannot be faked is a path that starts at your key. Your tribe is:

and no further. Two hops. Past that, "vouched for by someone vouched for by someone I once met" is a stranger with extra steps.

The header says you vouched or vouched by someone you vouched for. It never shows a number, a percentage or a ✓ for this. A key outside your tribe gets no badge at all — a "0 hops" label would read as a score and stamp a trust-shaped mark on every stranger.

Your tribe is what makes the rest meaningful:

The first number is free to manufacture. The second is the part that carries.

What does not put someone in your tribe

Verified names

The design also supports names that provably map to a key — an ENS name such as alice.eth, confirmed in both directions, shown with a ✓. The code is in place but is not active in current builds. See status.