Silberengel @Silberengel - 1d
You were this many days old, when you found out that an event-store, with lots of constantly-redefined interfaces to other stores, clients, and servers, is a totally normal architecture, and is no excuse for poor software quality.
This was not the Nostr innovation. I've been working on systems like this, for nearly a decade. They're very common in business information systems. There are tried and true software quality and data quality techniques for dealing with this sort of architectural volatility.
Yes. Also, the atomic nature of the events. These are actually things that make Nostr _easier_ to use, than the more common patterns, as you never end up with events you can't identify or categorize, and you can have high server redundancy.
Yes, but it was a massive innovation. Someone had to think of that. In hindsight, it was inevitable.