dikaios1517 on Nostr: What client are you using that you have to manually scroll up to see new posts? Most ...
What client are you using that you have to manually scroll up to see new posts? Most clients start you at the top with the most recent note first, and then you scroll down, seeing the author's information first, then the content they posted, and finally reactions from others.
When new posts are added to the top while you are scrolling down, most clients offer some means of jumping back to the top to see them, which would then give you the same ordering of author info at the top, then content, and then reactions.
If a feed was in the reverse order, and new posts were added to the bottom, then you would just have the same problem you are talking about when you are scrolling up to see previous posts. You would see the reactions first, without context as to why they are there, then the content, without knowing who wrote it, and finally the author.
This might be "solved" if the client remembered where you left off in the chronology, so you would rarely be scrolling up. But that comes back to what I mentioned before about not needing any context from previous posts in the feed to understand the post you are currently reading. Clients don't "save your place" for you, because where you left off really doesn't matter for consuming microblogging content. There is no inherent requirement that the user see every post in their feed in the order it was posted like there is for chat feeds. One post does not organically develop from the post that came before it, and therefore none of its meaning relies on ensuring you read the posts in the order they were posted.
Now, you might be able to find a dev that agrees with you and wants to present kind 1 notes with the most recent notes getting added to the bottom of the feed as they come in, rather than the top, and saving where you left off so you are still almost always scrolling downward to see newer and newer posts, but I have yet to encounter one. Indeed, you are the first person I have encountered who wanted or expected that experience from a microblog feed. It may be something you would have to build yourself if you want to see it built at all.
When new posts are added to the top while you are scrolling down, most clients offer some means of jumping back to the top to see them, which would then give you the same ordering of author info at the top, then content, and then reactions.
If a feed was in the reverse order, and new posts were added to the bottom, then you would just have the same problem you are talking about when you are scrolling up to see previous posts. You would see the reactions first, without context as to why they are there, then the content, without knowing who wrote it, and finally the author.
This might be "solved" if the client remembered where you left off in the chronology, so you would rarely be scrolling up. But that comes back to what I mentioned before about not needing any context from previous posts in the feed to understand the post you are currently reading. Clients don't "save your place" for you, because where you left off really doesn't matter for consuming microblogging content. There is no inherent requirement that the user see every post in their feed in the order it was posted like there is for chat feeds. One post does not organically develop from the post that came before it, and therefore none of its meaning relies on ensuring you read the posts in the order they were posted.
Now, you might be able to find a dev that agrees with you and wants to present kind 1 notes with the most recent notes getting added to the bottom of the feed as they come in, rather than the top, and saving where you left off so you are still almost always scrolling downward to see newer and newer posts, but I have yet to encounter one. Indeed, you are the first person I have encountered who wanted or expected that experience from a microblog feed. It may be something you would have to build yourself if you want to see it built at all.