<oembed><type>rich</type><version>1.0</version><title>Micael wrote</title><author_name>Micael (npub1f4…2a37d)</author_name><author_url>https://nostr.now/npub1f4q60j7fklm7sjzdz4ye42g5r3elnguuxajuch2kx8apulfkx0xqf2a37d</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>NOSTR is NOT dead&#xA;&#xA;The question isn&#39;t &#34;how many people are posting notes on Damus or Primal right now?&#34;  — it&#39;s &#34;what is being built on top of this protocol?&#34;&#xA;&#xA;And the answer is: a surprising amount.&#xA;&#xA;The protocol is maturing from &#34;decentralized Twitter&#34; into a general-purpose coordination and identity layer. The social media use case (kind 1 notes) is just one application among many now.&#xA;&#xA;The protocol is diversifying vertically into infrastructure. The pattern is:&#xA;&#xA;Identity layer: Your NOSTR keypair is your sovereign identity across all applications — social, commerce, development, AI, etc. No platform owns it.&#xA;&#xA;Event fabric: Signed, relayed events become the transport for everything — not just notes, but marketplace orders, git commits, AI requests, etc.&#xA;&#xA;Payment rails: Lightning and Cashu integration is native, not bolted on. Value transfer is a first-class protocol action.&#xA;&#xA;The critique about small user numbers misses that NOSTR is following a trajectory closer to TCP/IP or SMTP than to Instagram. These protocols weren&#39;t judged by &#34;daily active users&#34; — they were judged by what got built on top of them. Email was an application that emerged from a protocol.&#xA;&#xA;The architecture is sovereignty-preserving by design, instead of by policy.&#xA;&#xA;Cypherpunks write code; and it was never so easy as it is right now. </html></oembed>