nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcewvzaw você saberia me informar porque quando faço um quote com comentário no nostr:nprofile1qqs8834mjfzq4y6yy70h5d428hshzry3nzc7n69rjnx38cxatjv5cccpr4mhxue69uhkummnw3ez6vp39e3x7mr59ehkyum9wfmx2u30qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uqs7amnwvaz7tmev4ehgu3wd4jj7j7e69h, aparecem duas notas no nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt, tanto o quote isolado e outra nota com o quote mais o comentário. Acho que deveria aparecer só a nota com o quote e comentário. 

 Acho que o highlighter gera 2 eventos quando vc escreve um comentario. 

nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0y8qdrm is highlighter going with the `comment` idea from nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qdwkdtx or are you creating a separate kind 1 post for the quote when the user adds a comment? 

 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