My opinion might evolve, but this might be the first "nostr" problem. The cat is out of the bag, nostr is being developed on, and there seems to be nothing in the standards around how to format and interpret the payload.
Which is awesome if you want to build a BTC transaction system on top of it. But for ordinary microblogging, less so?
This will probably evolve, but we're going to see the most user-friendly and feature-rich clients develop their own standards for the message bodies, and nostr will effectively Balkanize around how clients accomplish text formatting, imaging, etc.
I guess this is solved with EVENT "kind", but kind is...integers, which implies the need for a registry and inevitable conflicts.
(sigh)
Decentralization is hard. nostr is literally repeating the charset "code table" problem in another form.
>From: TrentonZero at 08/13/22 12:28:06 on wss://nostr-pub.wellorder.net
>---------------
>Ah, the quotes are supposed to go at the bottom.
>
>...
>
>Who does that?!?
>
>>From: TrentonZero at 08/13/22 12:11:16 on wss://nostr-pub.wellorder.net
>>---------------
>>Hmm, the default more-speech behavior of adding quote blocks on a reply is not ideal for more-speech's own UI. The list view becomes filled with the reply text. This is, of course, only true without a subject, but no one seems to be actually using the subject field.
TrentonZero /
npub1sz…4g279
2022-08-13 17:35:59
in reply to nevent1q…luyr
Author Public Key
npub1szvxprymkgvxclns7rk4czsz79z50fkpenvfusgcq67ptlvctqws54g279Published at
2022-08-13 17:35:59Event JSON
{
"id": "95264a093e0ce8f29ac1899b933b95d3de032b7ed8f70c28e848fa46c536501a",
"pubkey": "8098608c9bb2186c7e70f0ed5c0a02f14547a6c1ccd89e411806bc15fd98581d",
"created_at": 1660412159,
"kind": 1,
"tags": [
[
"e",
"ab5444103edc86d31120aa97caaae923270332931d40660a935ce15e0e014c98",
"",
"root"
],
[
"e",
"8e77fbbaf92b0eea18a57072cd76022094d333b4ce3ab0cc207f18e2c5d24575",
"",
"reply"
],
[
"client",
"more-speech - 202208050837"
]
],
"content": "My opinion might evolve, but this might be the first \"nostr\" problem. The cat is out of the bag, nostr is being developed on, and there seems to be nothing in the standards around how to format and interpret the payload. \n\nWhich is awesome if you want to build a BTC transaction system on top of it. But for ordinary microblogging, less so? \n\nThis will probably evolve, but we're going to see the most user-friendly and feature-rich clients develop their own standards for the message bodies, and nostr will effectively Balkanize around how clients accomplish text formatting, imaging, etc.\n\n\nI guess this is solved with EVENT \"kind\", but kind is...integers, which implies the need for a registry and inevitable conflicts.\n\n(sigh)\n\nDecentralization is hard. nostr is literally repeating the charset \"code table\" problem in another form. \n\n\n\n\n\u003eFrom: TrentonZero at 08/13/22 12:28:06 on wss://nostr-pub.wellorder.net\n\u003e---------------\n\u003eAh, the quotes are supposed to go at the bottom. \n\u003e\n\u003e...\n\u003e\n\u003eWho does that?!?\n\u003e\n\u003e\u003eFrom: TrentonZero at 08/13/22 12:11:16 on wss://nostr-pub.wellorder.net\n\u003e\u003e---------------\n\u003e\u003eHmm, the default more-speech behavior of adding quote blocks on a reply is not ideal for more-speech's own UI. The list view becomes filled with the reply text. This is, of course, only true without a subject, but no one seems to be actually using the subject field.",
"sig": "b7421a78a13c22b80f6189d2b36f69c7bdbee71fb9f0b3614782d9b5fc3d5a03b5b693ff6d12084b914e7da456f24eaf8faf97da10db16c35e558ece5b2d49dc"
}