Info
Nostr (Notes and Other Stuff Transmitted by Relays) is a completely free and open-source protocol that nobody controls. It enables social media and many other applications without creating walled gardens or centralized platforms.
This Nostr social client is one of many clients that exist.
Nostr is modular and evolves through Nostr Improvement Proposals (NIPs). Because clients share the same open protocol, users are free to choose whichever client they prefer. Unlike centralised platforms like X and Meta, your digital self and data are free to move between clients, rather than being locked in and weaponised by some CEO.
Learn more at nostr.org
This client uses
NIP-01 The basic protocol: signed events, filters, relay subscriptions, event validation, and relay publishing.
NIP-02 Contact lists, used for follow lists and follow-list publishing with relay hints preserved where possible.
NIP-04 Legacy encrypted direct messages between users; useful for compatibility, but can leak metadata.
NIP-05 Human-readable identifiers like [email protected] that resolve to Nostr public keys and relay hints.
NIP-07 Browser extension login and signing, so users can publish without giving the app their private key.
NIP-09 Deletion requests, used when editing your own short notes by publishing the corrected note and disowning the old one.
NIP-10 Thread and reply markers for building conversations around notes and publishing marked replies.
NIP-11 Relay information documents, used to understand relay capabilities, limits, and supported NIPs.
NIP-15 End-of-stored-events notices, used by relay queries to know when the initial batch of stored events has finished.
NIP-17 Modern private messages, read and published as gift-wrapped events when the active signer can handle NIP-44 payloads.
NIP-18 Reposts, used for repost counts and publishing shared notes without copying the original content.
NIP-19 Readable Bech32 identifiers such as npub, nsec, note, nevent, and nprofile.
NIP-21 nostr: URI links, so Nostr references in notes can be opened from the client.
NIP-24 Extra profile metadata fields such as display names, banners, websites, and other common profile details.
NIP-25 Reactions, used for like counts and publishing reaction events.
NIP-27 Inline references, used to turn indexed profile and note mentions into clickable links.
NIP-36 Sensitive content labels, used by the feed filters to keep warned content out of the default feed.
NIP-40 Expiration timestamps, used to hide expired events from feeds.
NIP-44 Versioned encryption, used by modern NIP-17/NIP-59 direct messages when the active signer supports it.
NIP-45 Relay COUNT queries, used best-effort for reply, repost, and reaction totals when relays support it.
NIP-46 Bunker remote signing, used to connect to a remote signer for login, event signing, and supported DM decryption.
NIP-50 Relay search, used here to suggest profiles while editing follow lists.
NIP-51 Standard lists, used for mute lists so hidden accounts stay out of feeds and notifications.
NIP-56 Reports, used to publish report events for spam, abuse, and unsafe content.
NIP-57 Lightning zaps, used to request invoices, render QR codes, and listen for zap receipts when the recipient supports them.
NIP-59 Gift wraps and seals, used to route modern private messages without exposing the inner chat event publicly.
NIP-65 Relay list metadata, used for sane relay discovery and publishing a user’s read/write relays.
NIP-92 Media attachments, used to read imeta tags such as alt text, dimensions, blurhash, and fallback URLs.
NIP-94 File metadata responses, used when upload services return Nostr file metadata alongside media URLs.
NIP-96 HTTP file storage integration, used for profile image and banner uploads where supported by the media host.
NIP-98 HTTP authentication, used to sign upload requests without exposing the user’s private key.