Add to the record

Write a kind-30828 card: start a timeline, add an entry to someone else's, or revise a card that is already there. Your key signs it, the relays keep it, and the viewer reads it on the next load — nothing here is stored on a server. How to write one · the spec.

1sign in

A card is a record. A record needs a real key behind it — no throwaway identity here. Three ways in, easiest first. Use the one you already have. The last two come back on their own next visit; the secret-key rung never does.

No key yet?

Skip the next one. Install a browser extension — nos2x or Alby — and let it make a key for you. Then come back to the rung it points at.

Secret key

Paste your secret key here if you are brave and have a stomach of steel… yeah, don't do that with your nostr key.

Or even better — use a throwaway key!

start here

Browser extension

An add-on in your browser holds your key. You click, it signs. Your key never touches this page. nos2x · Alby · Nostore · NIP-07

Remote signer

Your key lives on your phone or another device. Every signature asks that device first — you approve it there. Paste the bunker:// address your signer app shows you. NIP-46

2the card

One fact per card. The collection is the timeline it joins — pick an existing one or type a new slug, which is all it takes to start one.

3revises another card — optional

Leave this alone for an ordinary card. Pick a card here and yours becomes a revision of it: the viewer draws the lineage, and if your content carries djot marks — {-removed-} and {+added+} — it renders as a diff against what that card said.

revise a card that isn't in the list

These are what actually get published; the picker above just fills them in. Both halves are required — the coordinate survives an edit of the target, the event id pins the exact version you revised.

4preview

The viewer's own card, rendered from what you have typed.

the event that will be signed

    

5publish