42
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2025
42 points (100.0% liked)
Lemmy
13929 readers
12 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 5 years ago
MODERATORS
Here is a reference to what that looks like.
I'm not sure how much I like the presentation here. Another option would be to have tabs between the sorting options and the comments.
If you want to combat people only contributing to the most active thread, maybe sort each instance's comments by total comments ascending?
If you wanted to leave a top-level comment in the other thread from the view you were in, you could do like a Window Shade type UI where each comment section is contained in a box with a clickable header. Clicking the header collapses the shade, leaving only the header. Kind of like collapsing a comment. The other thread comments could be under the primary thread comments and collapsed (or auto-expanded; maybe that's a UI setting). Like this:
| Comment Thread 1 (12 Comments) (community-a) |
Comment 1 | Comment 2 | Comment 3 | | Comment Thread 2 (12 Comments) (community-c)| | Comment Thread 3 (12 Comments) (community-d)| | Comment Thread 4 (12 Comments) (community-e)|
I was just suggesting this but in general.
It's awkward for me because the comment feed feels very segmented. It's awkward to have a big header for a smaller/niche instance and one comment below it.
It makes that comment seem like an orphan and gives prominence to people who use the biggest instance.
I'd also want the sort I apply (Hot/New/etc) to apply to every comment, not per instance.
I'd propose something like this.
Clicking on the Server dropdown could be a simple checkbox group, which would remember your configuration across that instance. That way, if you wanted to hide specific communities from appearing, you could.