It's hard to know when things are actually a thread and when they are just disjoint posts posted at the same time :(
Another small request for Amethyst, nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z: if an author makes subsequent notes (a thread) it would be nice if that thread is recognized. Now the rest of the thread is burries by newer replies from other people.
Not sure what the heuristic is though. Maybe first reply from the author is the next note in the thread, recursively.
While typing this, it probably warrants a thread view, which is slightly different compared to a note view in how notes are ordered.
See this note:
Discussion
Isn't a thread (as in the twitter terminolofy) just a sequence of notes by the same author, same parent, linked together through the e tag?
From the above note, REQ on author + parent, start at the oldest note, and see if that note is also referred in the chain, and work down recursively.
If they are disjoint, they don't refer to each other. Or if someone else is in between, the thread ends.
I don't know how much work is done in the backend or if everything is ordered on the front-end, so it can be either trivial or excruciatingly difficult :-)
ohh interesting.. Chase replied to each post. That's a lot of work. I will have to think through this.
If an author replies to his own thread and not to a reply, it should look like a singly linked list. Isn't this easy to detect?
I didnt say that right. If an author replies to his own replies directly to his own original top post, that should look like a singly linked list. If he replies to someone else's reply, that shouldnt be considered part of his own thread. This concept of threading is an artifact of twitter's post char limit but it could also be used to separate paragrapgs, thoughts, chapters, maybe even 'episodes' on nostr.
Yep that works. I just have never seen people going to the trouble of replying to each of their notes to create the thread.
Its common practice on twiXter or whatever its called now
Yep, but on Twitter it's a lot easier to create the chain at once. I don't know any Nostr UI that is creating many posts in a thread at once.
I agree it might be difficult to identify the entire thread since its actually a reverse-linked-list from the top (the first post is actually the end of the list). To find the next element, you need to load all replies anf see if the same npub replied directly to itself.) But if you recurse in a limited fashion (maybe load only 3 or 4 elements of the thread at a time with a "show more" to avoid infinite/circular thread attacks) it should be functional and it will allow viewers to see the next post in the thread right away. It could be as simple as just putting the authors direct replies at the top of the response list.
But the reason all of that was needed on Twitter in the first place was because of size limits. Those don’t exist on Nostr so we can post everything all at once instead and use other tools to reply to specific portions.
That was a posting optimization that was added much later to twitter. People have been doing tweet threads for at least a decade