If you think the spec could be accomplished in a better way, please let me know. I know the stringified json is blegh but i think it accomplishes the best given the compromise of mixing nips 23 and 51, and has a nice equivalence with nip01.
Discussion
I just came here to bitch about the spec actually and found this note from you 😂
yeah, I mean, the stringified. JSON in the content makes my skin itch; it's a horrible horrible horrible practice that is almost always unnecessary..
JUST MAKE THE K/V JSON TAGS!
"content": {'title':
👇
[ "title", "article-title" ]
[ "author", "author" ]
When in doubt, doing the same other events are already doing is preferable, specially when this is so painfully close to a list of NIP-23s and NIP-23 has title tag, why shoehorn it into the content? WHYYYY?
I don't think 30042 needs to be speced, it's literally just NIP-23 with a different kind number so chapters/modules don't leak into long-form clients. The spec should better by "30042 is whatever NIP-23 says".
Yep, all great points! PLEASE modify as you think works best!
I know its sooo similar, but functionally it opens some interesting experimentation. Needed to get some demonstration of it even if hideous 🤣
Yeah, I also prefer it in tags. 😂 We were just discussing that last night.
nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf are you up for that change?
I'd like to have the uploader match his viewer.
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku hold off on the uploading until they finish figuring out the final structure of the tags, please.
I'm just gonna work on my markdown doc and the formatting, tonight, so that they don't have me breathing down their neck. 😂 That's already hours of work, so here goes...
all good, i just got my hands on a nice wysiwyg md editor, typora, gonna start composing texts ready for it anyhow
it's a great exercise for me... it's using the computer and reading the old texts at the same time