Nostr Implementation Possibilities (mirror)

Groups whose membership and rules are enforced by the relay hosting them, identified by an id scoped to that relay.

Nostr Wallet Connect, where a client drives a remote Lightning wallet through encrypted events.

Kind 39701, a web bookmark addressed by its own URI, editable by whoever saved it.

Code collaboration on Nostr: repository announcements, repository state, patches, and issues.

A marketplace protocol built from stalls, products and order messages, kept for the clients that implemented it.

Remote signing: a client sends signing requests over an encrypted channel to a signer that holds the key and never surrenders it.

The list kinds, with public entries in the tags and private ones encrypted in the content: mutes, bookmarks, relay sets, follow sets and the rest.

A JSON-RPC API over HTTP for administering a relay: banning keys, allowing kinds, listing what it refuses.

How a relay advertises the roles it grants and the membership it enforces, and how a client asks to be admitted.

The versioned encryption format the rest of Nostr builds on: secp256k1 ECDH, HKDF, padding, ChaCha20 and HMAC-SHA256.

How an application declares the event kinds it can handle, and how users recommend one for a kind their client cannot open.

Static websites whose files are Blossom blobs, listed by a manifest event: one root site per key, and named sites beside it.

Kind 24, a plain text message addressed to one or more keys, meant for a notification screen rather than a thread.

Kind 30402, a classified listing: something for sale or on offer, with enough structure to be worth querying.

An HTTP file storage API discovered through a well-known document, replaced by Blossom.

Kind 1063, file metadata: the url, the hash, the mime type and the size of a shared file.

Data vending machines: paid jobs requested and delivered as events, reserving the kind range 5000 to 7000.

Assertions a trusted provider publishes about a key, an event or an external identifier, so a client does not have to compute a web of trust itself.

Kind 9802, a highlight: the passage someone found worth keeping, pointing back at the event or the URL it was taken from.

Negentropy over Nostr: range-based set reconciliation, so two sides transfer only the events one of them lacks.