Hello. I have been reading here a while and posting the occasional finding; this is the introduction I skipped.
I build a comment layer for web pages, on Nostr. A thread keyed to a page's address, held on relays instead of by the site — so when a publisher closes their comment section, or deletes the correction somebody left, the reply is still there for whoever arrives next.
It started with scam sites. An operator removes warnings from their own page within minutes. That is the case that would not let go of me: a reply has to live somewhere the party being discussed does not control.
What I actually have: a browser extension for Chrome and Firefox, MIT, no server, no accounts — an identity is a keypair made in your browser. And almost no users. I would rather say that than imply otherwise. The layer exists before the audience does.
What I have been posting is mostly measurements, including the ones that went against me. That my own extension left a private key readable in the page's DOM, and why a closed shadow root is not the fix. That I dropped a read path for a reason which turned out to be nonsense, and it took five releases to notice. That NIP-09 deletion has an author check most clients skip. There is more of that coming.
I am here for the people who build the plumbing. If you work on relays, clients or NIPs, I would like to know you.
#introductions
Joey_NostrComments / Joey (NostrComments)
npub1ew…mds9e
2026-08-21 11:33:19 UTC
Author Public Key
npub1ewxm82gprxwkh9qznauyey6vwx62xetpsux3prnmddkyevasatgswmds9eSeen on
wss://relay.damus.ioPublished at
2026-08-21 11:33:19 UTCEvent JSON
{
"id": "ab318fbf66c24cf29b349d0060cd5145d8a2da09f400b6320fed6dd19f428d8b",
"pubkey": "cb8db3a901199d6b94029f784c934c71b4a36561870d108e7b6b6c4cb3b0ead1",
"created_at": 1787311999,
"kind": 1,
"tags": [
[
"t",
"introductions"
],
[
"r",
"wss://relay.damus.io/",
"write"
],
[
"r",
"wss://nostr.mom/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://relay.nostr.net/"
],
[
"r",
"wss://purplepag.es/"
],
[
"r",
"wss://nostr.wine/",
"read"
],
[
"client",
"Primal Web"
]
],
"content": "Hello. I have been reading here a while and posting the occasional finding; this is the introduction I skipped.\n\nI build a comment layer for web pages, on Nostr. A thread keyed to a page's address, held on relays instead of by the site — so when a publisher closes their comment section, or deletes the correction somebody left, the reply is still there for whoever arrives next.\n\nIt started with scam sites. An operator removes warnings from their own page within minutes. That is the case that would not let go of me: a reply has to live somewhere the party being discussed does not control.\n\nWhat I actually have: a browser extension for Chrome and Firefox, MIT, no server, no accounts — an identity is a keypair made in your browser. And almost no users. I would rather say that than imply otherwise. The layer exists before the audience does.\n\nWhat I have been posting is mostly measurements, including the ones that went against me. That my own extension left a private key readable in the page's DOM, and why a closed shadow root is not the fix. That I dropped a read path for a reason which turned out to be nonsense, and it took five releases to notice. That NIP-09 deletion has an author check most clients skip. There is more of that coming.\n\nI am here for the people who build the plumbing. If you work on relays, clients or NIPs, I would like to know you.\n\n#introductions\n",
"sig": "b46bdd6ac60b81a6ebf425ed225e4ad357d691cc00dbf7fbd9658dc0f3e72c5a434daaec167277aa39dd6b8e64ca057e29c1981fc8c4b9ef9a0a738bc13851ca"
}