I think client development was the first epoch of nostr, building windows onto the protocol. The plethora of web-apps and packages, downloaded and run across browsers and operating systems that share nothing. Each of them re-implements trust, identity, storage from scratch or tries to bridge the signing experience.
The next epoch is nsite browsing. And the endgame is nostr-native OS. It completely shifts how we use the protocol.
Nsites change where the app lives. It's a signed object now, addressed by a key, loaded and verified on your own machine. No host to trust. No gateway to demote it back into one. The browser verifies every blob itself and 'bad' servers get skipped, not trusted.
So the layers collapse. Client, app, browser trust decisions become one nsite browser or OS running on your hardware, signing and verifying. You stop downloading separate apps or clients and start loading artifacts into a context that's already yours, already signed in.
That's the epoch I see around the corner. Apps that compose because they share the same signed-in context. nostr is the entry point with no app store, no client. The same nostr, used the way it was always shaped to be.
Yes, you still install the browser or OS once. But it needs to be nostr-native from the first touch. Same shape as http today, one runtime, infinite signed artifacts. The boundary you used to redraw per-app is now drawn once, at the runtime.
The protocol doesn't change itself, just how it's applied. Software stops being something you download and assemble and simply starts being something you enter, signed in, private by default.
quotingWild.
nevent1q…fzy6
Disclaimer. I barely know what I'm talking about.
nevent1q…7dpe