I wanted it to be a different kind but so many clients do quote repost this way I didn’t want to create more work for everyone by creating another repost spec no one likes.
🤔
interesting approach, nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s; this does mean that you can't query for the quote reposts of a note though
not sure how I feel about that, maybe it's a feature not a bug? 🤷♂️
Discussion
I appreciate that; I was writing https://zapworthy.com this morning and getting it to parse mentions in the new way felt like redoing a bunch of work.
Appreciate you 🤝
If we really care about counting quote reposts we can make it a new kind in the future.
it could also be a different. non-`e` tag, but that might be asking for trouble
designing from first principles this would probably simply be a different kind
Why would this be asking for trouble ? I’ll use q tag nostr:note1qq854j25xc8djtfzhse0qavk6kac4rmwkascf06ueq7dep650w5s2j6p0j
I really just don’t want these taking up precious space in the thread filter. So either we change kinds or use a different tag for references. I think a different tag is ideal. I’ll use q.
I thought about it a bit more and the quote repost without a tag breaks data links; it’s not just about the counting of reposts.
A conversation around a quoted event has some kind of relevance to the quoted event; it would be nice to be able to show those offshoot conversations from it.
(I’m thinking, what happens when someone embeds a 9802 event on a 1 note?; I’d like to show those discussions as children of the 9802)