Nested Replies feature released recently

@jonathandekhtiar and I tried this during the EuroPython sprint just now and it’s indeed unacceptable as a default view. You can see it in action in this topic.

The nesting is a welcome visual improvement, however it seems to us it should be selectable by the viewer, not the topic author. When it is forced on all readers, we expect people will complain. Especially that the nested view’s got a few non-trivial issues that don’t make it a clear improvement.

We cannot enable that for everyone in the current state.

A summary of issues we found

Getting to the latest reply is not obvious

This scrollbar on the right is gone with nested replies:

This makes it hard to tell if you’ve read everything.

Sorting of the nested replies is kind of surprising

Regardless of whether “old”, “new”, or “top” is chosen, every tester at the sprint was confused. It’s probably obvious to Reddit users, but it’s a big departure from the previous obvious “time goes down” sorting.

Like, why in the screenshot beloww is @Quercus’ reply above mine? Mine was posted sooner! It’s no longer sorted by “old”, right?

Deeper replies are flattened and hidden by default (?)

There’s a default 3-level limit for replies. In the screenshot below @hugovk and I replied to @Quercus, but those replies got flattened and now they appear after my reply to Hugo. This makes it super confusing and is by itself a deal breaker:

Linking to a post shows a subtree

There’s a subtle bar telling you this, but it’s easy to miss it and get confused.

Mobile rendering is pretty broken

This is clearly not finished.

8 Likes