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':, 'author':, ...} ,

👇

[ "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".