Nostr Web Client

I would not assume `e` tags are necessarily part of the thread. It all depends on the marker in the new system. And people can create any marker they want.

jb55 2y ago

kind1 Thread queries (#e) can’t distinguish between thread replies and non-threaded kind1 notes. So you are forced to pull them down when you don’t need them. This is not good, especially if there are lots of quote posts of the root note.

I could of course filter them out and probably should, but I would still rather not pull data that I don’t need, especially if it reduced the number of real replies in a limit query.

Let’s say there are 105 newer kind1 quote reposts of some thread, and 1 reply. A {#e: threadid, limit:100} would fail to fetch the replies on the thread.

This is only an issue because quote posts are kind 1. A quote repost spec with non-kind 1 and etags would work too.

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 2y ago

I don't disagree that is not ideal.

My only point is that you should not assume `e` tags are necessarily part of the thread, especially when they have a marker on it (any non-root, non-reply marker).

ryzizub 2y ago

Yeah, I think we're somewhat on the same page. I've already made some post around this topic, where I mentioned that we use multiple versions of quoting.

I believe having a tag with a mention marker is still useful, as I often see quotes used as comments, they are just quoting to get more attention. They're still contributing "comments," but in a different type of post.

However, separating this as a 'repost' is the better approach.

It might be a good idea to move this discussion to GitHub from now on.