A good compromise is to post the use-case-specific kind, then quote it in a kind 1 to advertise its existence. This also encourages clients to either implement render support for the new kind, or advertise alternative clients via NIP 89.
Login to reply
Replies (1)
This is the way, also kind 16 "shares" can be useful