Open ggtylerr opened 5 months ago
My personal preference would also be to list child comments chronologically (oldest first), that's how it is done on most platforms I know which only allow for 1 level of nesting.
Hello cal is not working for Invidious Piped Beatbump Hyperpipe
Hello cal is not working for Invidious Piped Beatbump Hyperpipe
You're on the repo for the commenting system, not in the comment section...
Looking at this a second time, I noticed this has the "needs-decision" tag. I don't know the internal discussion, but IMO it's down to two choices:
If both are to be considered, you can have the first come in on v0.13.1, and the second come in v0.14.
Since no one else has weighed in on this issue so far, I'm making the decision to go with option 1. @ggtylerr it would be great of you to implement the change in a PR.
Edit: Please don't forget to also change the documentation to mention that as of 0.13.1 (?), reply sorting reverts back to oldest
.
Sure, I'll try my hand at an implementation in a few.
Checklist
master
branch does not fix my issueWhat is not working?
When using the new sorting system introduced in #1005, replies are sorted the exact same as regular comments. If comments are sorted by newest first, the replies to said comments will also be sorted as such. This can potentially confuse the reader, as the reading order for threads is usually always oldest first. Here's an example of what it looks like now: Note how the thread starts with the oldest post (the OP), then immediately after that, the newest post (the reply.)
How can one reproduce this issue?
On the client-side configuration, set
data-isso-sorting
tonewest
. (This is possibly also visible inupvotes
too, but haven't tested yet.) Then, post a comment, and reply to it at least twice.