I'm with you on the whole "organising Nostr chaos" thing... That's basically what I try to do as well. Much less successfully than you, though, as I don’t even propose a lot of stuff... More like try to fix existing standards and tooling in a minimal way.

Still, I care about a lot of the same things as you. Actually, I care to the point of pestering you multiple times about the NIP-05 vs NIP-65 bootstrapping ambiguity, and pestering, well, just about every dev on Nostr about implementing proper Outbox model support, leveraging DHT to avoid centralisation on the bigger "indexer" relays, sending the right kinds to the right relays, supporting NIP-17, NIP-29, etc., etc., etc. I also like the idea of more formal contracts, and possibly evolving beyond signed JSON over websockets.

I think a lot of devs on Nostr are thinking along similar lines. We (or at least I) just lack a good way of reaching out to each other. I don't have a "Gossip" or "Nostr bootstrapping" forum to reach out to you, no NIP-29 group, no IRC, XMPP, Matrix or whatever that I can join to discuss this kind of stuff. I’ve got too many notifications on GitHub to even bother. And as much as I love pestering fiatjaf, Vitor, etc., there’s only so much that can be done via Kind 1 or DMs theis way. I think if we can put some effort into organising communication channels beyond PRs and comments, we’d stand a much better chance of driving this kind of effort forward.

I don’t know much about Mosaic, but it sounds like a heck of an interesting greenfield project. All greenfield stuff is amazing, beautiful, and promising. Nostr has this “ever-greenfield” attitude, which I totally get. But the fact is, there’s already enough "legacy" on Nostr. We need to start managing it like every project that’s survived a couple of years beyond MVP. Get the communication structures in place, and the right people will come together to drive the architectural changes you’re looking forward to.