Replying to CodeWarrior

Yes, entirely. I beleive json in content is good. I have a git repo in my metadata.

But I know from experience that at least 1 popular client, which I'm not going to name,

tries to parse everything that has a dot in it as a link, and anything with a # as a tag.

There should at least be an option to turn that off. But yeah, client problem, not mine.
Avatar
Zach 2y ago

Yeah I know which one you mean and that’s annoying as hell.

You’re totally right that json contents would (at least at first) net increase client issues. I think that’s not a compelling case for the prohibition of json contents though. Especially if there were a dedicated kind that was associated only with json contents.

Reply to this note

Please Login to reply.

Discussion

Avatar
PABLOF7z 2y ago

no one is talking about prohibition

you can do the same thing, sticking json in an event, without putting it in the content and allowing clients to almost-always be able to present something that is human readable; just put it in a tag, like nip-57 does

Avatar
Josua Schmid 2y ago

I always understood kind 1 as plaintext.

But there is no such thing as plaintext.