NostrComments

Comment freely on any website — without censorship, powered by Nostr. NostrComments adds a floating button to every webpage that opens a decentralised comment thread. Comments are stored on public Nostr relays — not controlled by any website, platform, or algorithm. WHY? News websites and social platforms routinely delete or hide comments. NostrComments lets anyone leave a comment on any URL that no website can remove — it never lives on their servers in the first place. WHAT IT IS FOR - Warning the next visitor: a shop that never delivered, a seller who vanished, an offer that is too good to be true. One comment already helps the next person, even if nobody ever replies. - Discussing the news on sites that closed their comment section. - Adding context to a company announcement, a government page or a press release. SEE IT BEFORE YOU INSTALL IT This extension asks to run on every site you visit, which is a lot to grant something you have not seen. So you can read a thread without installing anything: https://briskness-byte.github.io/thread/ — paste any address and it shows the comments filed under it, queried from the same public relays, straight from your browser. GETTING STARTED No account needed. Click the button and generate a key in one tap — your identity is a cryptographic keypair stored in your browser. Already use Nostr? Connect a signer extension like Alby or nos2x and keep your existing identity. FEATURES - Works on any website - No account, server, or sign-up required - Built-in key generation — no external wallet needed - Optional password encryption of your key at rest - Portable identity — copy your key as nsec / npub for any other Nostr app - Shows what the wider Nostr network has said about the page, not only comments left here - Upvote / downvote with community auto-hide - Delete your own comment — publishes a NIP-09 request; relays that honour it drop it - Mute users, and mute any word or phrase you choose - Optional verified names (NIP-05), off by default because checking one contacts that domain - Comments posted since your last visit are marked "new" in the thread - Reply threads, notifications that name the page, search, and sort (newest, oldest, most upvoted) - Share a comment to your Nostr feed as an ordinary note, behind a confirm - Settings lists the pages you have commented on, so you can find a conversation again - Repeated near-identical comments from one key fold into one line, with the rest a click away - Pictures and avatars can be held back until you ask for them, host named before you do - Zap comments with Lightning - Inline images and video, dark mode, custom relays - Move the button to whichever screen corner is free, remembered per site - Per-site disable option - Open source: github.com/briskness-byte/NostrComments DATA DISCLOSURE NostrComments has no server and the developer receives no data. There is no account, no tracking, and no analytics. Nothing is transmitted until you explicitly enable the extension on a one-time disclosure screen. After that: - Loading and posting comments: the current page URL, your comment or vote, and your Nostr public key are sent to the public Nostr relays you have configured. These are independent third-party servers, not operated by NostrComments. Since v22.53 a relay is only contacted once a page has actually been read — never for a tab you did not look at. - Extra relays for what you post (on by default, posting only): a comment held by a single relay is gone the day that operator decides so, which defeats the point of the extension. So what you post also goes to three relays that are never read from or queried - purplerelay.com, relay.nostrplebs.com and nostr.bitcoiner.social. They receive exactly what your own relays receive, plus your IP address as any contacted server does, and learn nothing about pages you only read. It can be switched off in Settings. - Deleting your own comment: a signed deletion request naming it is sent to those same relays. It is a request; relays that honour it drop the comment, and some will not. - Identifying yourself to a relay (NIP-42): some relays refuse to serve anything until a client proves which key it is. When one of yours does, a short signed event is sent that tells that relay your public key. Only ever in reply to an actual refusal, never because a relay offered. - Verified names (NIP-05), off by default: if you switch it on, the extension asks the domain a commenter claims whether that name really belongs to that key. That domain — a third party other than your relays — then sees your IP address. Off unless you enable it in Settings. - Profile pictures and images in comments: these load from whichever server the person who posted them chose, which gives that server your IP address and browser version. For an avatar that happens on every page where that person has commented. This is how Nostr clients generally work and the developer is not involved, but it is a third party you did not pick. Since v23.0.2 these requests withhold the page address (no-referrer) and load only as they come into view, so that third party is not told which page you are reading. - Zapping (optional): if you choose to send a Lightning tip, your browser contacts the recipient's Lightning provider to fetch an invoice, and your own wallet pays it. That provider sees the request, including your IP address. No payment code is bundled and no money passes through the developer. - Stored on your device only, never transmitted: your key (optionally encrypted with PBKDF2 + AES-GCM), relay list, muted users and words, per-site disable list, per-site button position, theme, which signer to use, whether verified names are checked, whether the extra publishing relays are used, your consent choice, a flag recording that you confirmed your key backup, a flag recording that you were offered key encryption, a flag recording that a support zap was sent, and a list of the last 300 pages where you opened the …