i'm of the opinion that events shouldn't have tags, tags should be in a context field of a specific kind, this would be one change i would make

i'm big on single responsibility principle, and more recently i have learned about Domain Driven Design... these two systems of thought about systems architecture both say you should keep things simple and tight, and use layering and not bake things with potentially different uses into a single monolith

and hey, that's one of the key disagreements between BSD/Darwin vs Linux/Windows kernels now

technically, the former is superior, more robust, more efficient, faster, lower latency, lower bug count, less exploits

but unfortunately the latter, in both cases, have proliferated like a virus

I would not put nip-65 into nip-01. I wholeheartedly agree with you that social networking is only a small part of what nostr can and will become.

But I do think there needs to be some advice about relay usage moreso than we have today, where clients fail to rendezvous and people try to fix that by blasting. Each use case will have potentially a different solution. I think inboxes and outboxes are general enough concepts to work in multiple use cases, but certainly not all, there are half a dozen use cases already that don't choose relays in that way (take nsec-bunker for example, or a livestream service, or relay-global feeds, etc).

I thought you said you think of nips as an ogre, I mean onion

a similar idea was the original thought behind wikifreedia.xyz

what "nostr" means might vary for different developers

I had originally thought of the idea that ended up as wikifreedia as an editor where you could define what each NIP is, and, even if we got to have competing NIP implementations, at least the competing proposals could be documented.

Sort of like what you have with the DIPs repo, where stuff that wasn't "accepted" into the nips repo can (and does) still exist and be easily documentable/findable.

This is genius. I've been thinking about various other applications that wouldn't operate well on the network as-is. I'm thinking beyond "social media protocol" and into "decentralized and distributed (platform-less) cross-application persistent identity, media storage and retrieval, and information security". Replace and tear down gatekeeping for MLS (real estate for those not familiar), for community governance (more secure and psudonymized voting, likely with a different npub), for commercial networking and markets with tiered profile structures, etc.

Having the option to branch the protocol to specialize into other applications that would simply not work well on a social-first paradigm would make these other ideas actually feasible.

Another reason I think this is the future is because AI is taking over so many spaces, but AI can't fake digital signatures, and the signing paradigm of Nostr is a shield against it.