What is Nostr?
unclebobmartin /
npub19mu…jnft
2023-06-11 16:03:26
in reply to nevent1q…694k

unclebobmartin on Nostr: From: pablof7z<-DerekRoss at 06/11/23 10:35:06 on wss://relay.damus.io > ...you’re ...

From: pablof7z<-DerekRoss at 06/11/23 10:35:06 on wss://relay.damus.io

> ...you’re constructing it in a way [that makes it] incredibly difficult for a client to parse all this ambiguous text into something sensible.

It's a free nostr, you don't have to parse it. I'm certainly not parsing it.

The bottom line is that there are going to be a vast number of different clients. Each client will be pursuing it's own particular use cases for nostr. Some of those use cases will be relatively incompatible with others. C'est la vie! The last thing we want is some kind of fixed UI standard that every client must adhere to. Such a standard would almost certainly restrict the number of possible use cases and make nostr a lot less free.

So, if you don't want to propogate the subject tag, don't propogate it. If you don't want to parse the embedded replies, don't parse them. If you want to use highligher, use highlighter. It's a free nostr.

CC: Vitor Pamplona (npub1gcx…nj5z)
CC: Kieran (npub1v0l…qj49)
CC: mikedilger (npub1acg…p35c)
CC: hodlbod (npub1jlr…ynqn)
CC: jb55 (npub1xts…kk5s)
CC: unclebobmartin (npub19mu…jnft)
Author Public Key
npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft