NIPs are client-client strategies. Move…

NIPs are client-client strategies. Move fast and break things.

It allows a rapid innovation process, at the expense of some techincal debt. At this point technical debt might actually be an advantage since nostr is ahead of other systems in some areas.

Structured data is applied at the bridges to allow interop. Even activitypub doesnt use RDF, their vocabulary is completely missing.

As long as you're not drowning in technical debt (nostr isnt yet) you can make progress with permissionless development, which is what the dev community want

As you grow and scale up, generalized patterns can be added, refactors, and achitectural elements such as caching, delivery networks, separation of concerns, side-effects, gossip and so on.

Scaling nostr is one of the next big challenges, but the path exists and has been navigated before.