However, I'll hypothesize that it's preferable (overall) to have more friction on collapsing comments. A lot of great discussion happens in response to even a mediocre top-level comment, and forcing the user to take a few extra moments to skim the child-comments will increase the serendipitous discovery of these nested gems. Furthermore, the problem of a mediocre top-level comment with mediocre nested comments being at the actual top of the discussion is mitigated by the ability for people to downvote the thread, as has been done (with varying levels of efficacy) until today.
Excellent phrasing. As a fairly long-time user who lurks more than he comments, I can concur that much of the best conversation I've read and participated in happened to be such nested gems. Serendipitous, indeed.
Is this actually data-driven or just a guess on your part? My experience is that a mediocre comment rarely ever gets good replies.
Maybe "mediocre" is the wrong word, as it implies an absolute judgment (on some non-existent scale of "quality"). I guess my intuition is derivative of the "don't judge a book by its cover", in that even if a submitted and upvoted story is not something I feel like reading, I still might read the comments to see the discussion.
Maybe someone internal to HN can do a quick calculation of how many child-comments surpass their parents (while accounting for the differences in visibility).
This design was the minimum change possible (which has a value, but usually a net negative one).
A subreddit I was on recently (sorry, can't recall which) has styled the collapse-sensitive region to be the entire indent region of a comment block. This is actually unbelievably awesome.
As long as the user is aware of the misclick, I don't see this as a likely problem, personally. Awareness of the misclick is, in my opinion, quite likely, given that they will see the arrows disappear and won't observe the expected thread collapse.
Both the username and the date are clickable links in the HN interface (to the user profile and the comment itself, respectively).
Until HN has a good mobile theme by default, I'd prefer collapse and voting buttons to be well separated from one another.
What I'd like to see is a control that takes advantage of this right-side position of the collapse button to add something like the following, perhaps only visible on rollover:
[-] all
In which the `all` link collapses all the way up to that thread's OP, immediately revealing the next thread below.Essentially, the left-hand indent zones are collapse regions for the post topping that level of the hierarcy. It's sheer brilliance.
Can't find the sub, though I've looked for it. I thought it was a science one. Maybe politics -- somewhere I don't often go. Hrm, no, not there either.
I think this old reference is on par with your comment, at least it's how I view and agree with it.
https://news.ycombinator.com/item?id=11355675
Realizing many comments down that you are wading into unwanted territory makes the side column incredibly useful to pulling the rip cord as it were.
Each comment has a significant vertical footprint(at least 2 lines after the upvote triangle) on mobile so maybe this opinion is biased, but I am also of the mindset that users shouldn't be alienated to a separate app to cover a relatively simple wart removal.
Heck, having a visible column in the left position to flick up or down for a collapse or return to parent becomes increasingly useful. But now I'm on a new tangent.
// ==UserScript==
// @name move_collapse_link
// @namespace com.kludgecode.hn.demo
// @include https://news.ycombinator.com/item?id=12073675
// @version 1
// @grant none
// @run-at document-end
// ==/UserScript==
window.$destination = document.getElementsByClassName('comtr');
window.$source = document.getElementsByClassName('togg');
for (var i = 0; i < $source.length; i++) {
var row = $destination[i].getElementsByTagName('tr')[0];
var cell = row.insertCell(0);
row.children[0].appendChild($source[i]);
}
Modifying the @include line by replacing the query portion of the URI with an asterisk, will cause the code to run on all HN "story" pages. Matters of preference ought to be within the users control. I like Greasemonkey/Tampermonkey because suddenly a lot of things are.Perhaps also adding the first line (truncated if need be) of the Parent's comment would be a nice addition also?
It would help when scanning all the collapsed comments and seeing some context other than the Parent's username?
Nevertheless these enhancements are much appreciated!
exact same thing happened on reddit when the feature was introduced
The new collapse button is at the end of the comment. This means that the collapse button's position on the page changes based on username length and duration wording (hours Vs. minutes, etc).
One nice thing about other websites which I won't name, is that you can read and collapse all of the top comments without having to "seek" the collapse button constantly. You can literally scroll and collapse as you read, it is always in the same spot.
The functionality is most welcomed, and I'd take this design over not having it. But it could be slightly better with a subtle design change.