Tend to agree, but kind 0 and kind 3 both use JSON strings in content and NIP-51 uses content for the encrypted lists, not sure about other kinds.

Maybe there are two parts. Previously I suggested another approach too - see below.

1. We should be able to reasonably have a kind to kind label mapping that can be used to at least give context in apps. That’s a step forward.

2. If that kind can somehow give a fallback content or similar, great. Maybe the equivalent to the noscript HTML tag or img alt attribute. Dupe data, but that’s life. A tag is better suited long term than the content.

Additionally, we could somehow have registrable Nostr event kind url handlers - so you can tap the placeholder to load it in a different application. I don’t know how this scales perfectly, as url handlers may not allow kind ranges.. but worth experimenting. Apps are likely linked to target kinds over ranges anyway.

No harm having a fallback comment. The user comment should be gathered from the zap request anyways so the zap comment could have anything in it. I don’t have much hope in everyone updating their zappers, but wouldn’t hurt.

I REALLY like the idea of keeping content human readable. I agree that JSON in content is an anti-pattern.

Problem: I need arbitrary JSON in events.

Solution?

I've gone through the "put it in tags" phase and nobody liked it.