If you need a protocol layer that you can rely on for mission critical applications, you are in the wrong place. Nostr-grade isn't going to cut it. But Pubky's architecture might. Check it out.

awesome-pubky

awesome-pubky

pubky.tech - all directory of pubky resources, libraries, tools and applications

From a UX perspective, whether or not other Nostr users actually recieve a note/reply/DM feels like an absolute lottery. This is a particularly grating when: - Composing the note/reply/DM has been a non-trivial effort - It's part of a multi-partite conversation that thus becomes fragmented. - I am actually friends with the person and the Nostr black box nonetheless decides to hide or not deliver my note. - I exchanged npubs with somebody to keep in touch, and at some unspecified point thereafter, DM's are expunged and/or stop working. Fucking up DM's is in itself an app killer. Everybody who's ever worked in any serious tech org knows this.

Turns out that if you criticise #Primal (i.e. for integrating Spark) you get banned from the relay.

Nostr's pathology report will highlight 'Lack of Bolt12' as one of the main reasons for its demise.

Replies that you can't see. *adds to list

Users would be forgiven for thinking that Nostr is an implementation of IRC for Windows 2000. That's how bad the UX is. Probably worse actually.