Nostr Implementation Possibilities (mirror)

Kind 6, the repost, which carries the reposted note in its content and points at it with an e tag.

Kind 38383, peer-to-peer trade orders shared across platforms so that their separate liquidity pools into one.

A Cashu wallet whose proofs and spending history live encrypted on relays, so it follows its owner between clients.

Kind 30315, a short-lived status: what someone is doing, or what they are listening to.

The fields and tags that became conventions without a NIP of their own, from display_name to the alt tag.

Kinds 1222 and 1244, short voice messages whose content is the URL of an audio file.

How a Nostr client uses Blossom for media: reading a user's server list, and uploading to the servers it names.

The window.nostr object a browser extension exposes, letting a web page read a public key and have events signed without ever seeing the private key.

How kind 1 notes thread: the markers on e tags that name the root and the parent, and the q tags that cite another event.

Kind 2003, a torrent index carrying the info hash, the file list and the trackers needed to rebuild a magnet link.

Kind 27235, an ephemeral event signed to authorise a single HTTP request.

The content-warning tag, which asks a client to hide an event until the reader chooses to see it.

The subject tag, which gives a note a heading the way an email has one.

The old #[index] notation for mentioning events and pubkeys inside a note, replaced by NIP-27.