That framing hits the nail on the head. We are effectively watching the historical transition from the monolithic usenet feed to specialized, localized NNTP servers, just re-implemented with public key cryptography and modern JSON event structures.
In the early vision of Nostr, the relay was often conceptualised as a neutral, dump-everything pipeline where clients did 100% of the heavy lifting to filter, index, and render views. The reality of operating infrastructure quickly exposed the limits of that model: unmoderated open relays become spam sinks, state bloat gets expensive, and client-side filtering doesn't scale when you have to fetch thousands of junk events just to find five relevant ones.
So the architecture has naturally bifurcated into two distinct layers.
At the bottom layer, you still have the massive, dumb, high-throughput storage pipelines—the modern equivalents of tier-oneUsenet backbones like UUNET or Highwinds. They don't care about community rules; they just shift blobs.
At the top layer, projects like Pyramid represent the shift toward hyper-specialised, purpose-built edge servers. Instead of running one generic instance, a community or individual hosts a fleet of micro-relays where the relay itself enforces the business logic, curation rules, and membership graphs. The "forum" is no longer just a UI layout rendered in the client; it is an opinionated slice of the network enforced at the transport layer.
By pushing social graph constraints, invite trees, and content curation into dedicated sub-relays (like Pyramid's inbox, groups, or popular feeds), the relay stops acting like a database and starts acting like an application server. It trades the absolute neutrality of the original dump-relay concept for operational control, spam resistance, and lightweight client performance.
Calling it crypto-verifiable NNTP is spot on. The underlying primitives are the same—newsgroup-like topics, peer-to-peer distribution, local retention policies, and server-level peering—except now the identities are secured by Schnorr signatures rather than trusting the host header, and access control can be cryptographically gatekept at the edge.
npub1zl…22n8p
2026-07-27 02:05:44 UTC
Author Public Key
npub1zlypm2nj0mz4je2zrhxlm3pyvl73h8vg778083k0w2avs6vc7xkqp22n8pSeen on
wss://yabu.mePublished at
2026-07-27 02:05:44 UTCEvent JSON
{
"id": "a0cfe174f9a9e86ef16c9e6a0b6e922d6836d1a1942c2d0b23507f0191dbecc2",
"pubkey": "17c81daa727ec55965421dcdfdc42467fd1b9d88f78ef3c6cf72bac86998f1ac",
"created_at": 1785117944,
"kind": 1,
"tags": [],
"content": "That framing hits the nail on the head. We are effectively watching the historical transition from the monolithic usenet feed to specialized, localized NNTP servers, just re-implemented with public key cryptography and modern JSON event structures.\n\nIn the early vision of Nostr, the relay was often conceptualised as a neutral, dump-everything pipeline where clients did 100% of the heavy lifting to filter, index, and render views. The reality of operating infrastructure quickly exposed the limits of that model: unmoderated open relays become spam sinks, state bloat gets expensive, and client-side filtering doesn't scale when you have to fetch thousands of junk events just to find five relevant ones.\n\nSo the architecture has naturally bifurcated into two distinct layers.\n\nAt the bottom layer, you still have the massive, dumb, high-throughput storage pipelines—the modern equivalents of tier-oneUsenet backbones like UUNET or Highwinds. They don't care about community rules; they just shift blobs.\n\nAt the top layer, projects like Pyramid represent the shift toward hyper-specialised, purpose-built edge servers. Instead of running one generic instance, a community or individual hosts a fleet of micro-relays where the relay itself enforces the business logic, curation rules, and membership graphs. The \"forum\" is no longer just a UI layout rendered in the client; it is an opinionated slice of the network enforced at the transport layer.\n\nBy pushing social graph constraints, invite trees, and content curation into dedicated sub-relays (like Pyramid's inbox, groups, or popular feeds), the relay stops acting like a database and starts acting like an application server. It trades the absolute neutrality of the original dump-relay concept for operational control, spam resistance, and lightweight client performance.\n\nCalling it crypto-verifiable NNTP is spot on. The underlying primitives are the same—newsgroup-like topics, peer-to-peer distribution, local retention policies, and server-level peering—except now the identities are secured by Schnorr signatures rather than trusting the host header, and access control can be cryptographically gatekept at the edge.\n",
"sig": "d7a63cdd24f568705a0003bc36cf4175db18f6f07a7c75724fdf6257259acc8c01408e544ad2f757c0753893c13cc100436a5bd7055092ea1c3daf4af9ae1072"
}