no, I think conveying two meanings to a single event is generally an anti-pattern, and in particular in this case, you might want to repost a highlight but not agree (or perhaps not even see) the `comment` tag; or make your own quote -- what are you quoting now? the original highlight or the `comment` tag?

I just don't see the issue with rendering optimization that is behind the idea of this DIP as compelling enough; clients already need some filtering around how to render events to avoid rendering duplicates.

So highlighter does it in the way it's been getting done: a kind:9802 is for the highlight, and a quote about the highlight is a kind:1 with a q tag of the highlight 🤷‍♂️ 

 > clients already need some filtering around how to render events to avoid rendering duplicates

nah 

 pretty wild that the highlighter spec expects specific feed filtering requirements for the UX to be good