i'm not gonna bother without a TLDR on why it's better, and if i read in that something about something that is a dressed up consensus, i gonna give it a hard pass.

i've been a student of distributed systems for a long time now, since 2013, and i know a consensus protocol when i see one. nostr doesn't have one, which is the first thing every newbie to it thinks is a deficiency and they crow about how they are going to make it better by adding a consensus to it.

no consensus in the spec means i can add any consensus i want for a specific purpose. if you bake one into the spec that interferes with the use case i have in mind, it's ruled out of the options i might choose.

the things i don't like about nostr are websockets and kind numbers and NIP numbers. those can be worked around and don't lock me into a range of architectures and exclude ones that i consider to be more useful.