2381 points by dang 3520 days ago | 451 comments on HN
| Mild positive Product · v3.7· 2026-02-28 11:06:03· from archive
Summary User Autonomy & Transparent Governance Advocates
This HN self-post announces five new platform features (comment collapsing, vote transparency with undo, saveable favorites, story hiding, historical content browsing) and introduces moderator sctb. While not explicitly framed as human rights advocacy, the announcement advocates for user autonomy, information control, and democratic participation through feature design. The moderator introduction emphasizes fairness and competence, suggesting platform commitment to equitable community governance.
Why is hiding stories available to logged-out users? Reloading just makes them appear again. :p (EDIT: may be bug)
On a related tangent, why have all instances of "submissions" on HN been replaced with "stories"? It's an change which IMO does not fit the usage. (A Show HN wouldn't make sense as a "story.")
Request: Feature 5 most-popular-by-day is almost exactly what I've wanted for a long time, except in RSS form - a feed that updates once per day with the top 30 stories from the previous day in the order of most time on front page. None of the external HN-specific RSS generators do it quite right.
Suggestion: Can you move the collapse button to the left of the username? One way I tend to use nested comment threads is reading all top comments, collapsing as I go.
How long does the "unvote" option last? Permanently? If I accidentally bump the "unvote" button on a comment that's years old, can I re-apply my vote, or only if it's an upvote?
Thanks dang et al. for doing such an absolutely stellar job. Even more than this steady stream of new features, the key thing I've been noticing for the last couple of years is a complete absence of laments about how things have been going downhill. Keep it up!
Dang those are some nice features! :-) I really really love the collapse feature. Does the collapse persist across new comments being added or are those not collapsed? We'll have to see.
And final thought on the stories/submissions vs comments the challenge is that comment is both a verb and a noun, you comment, and you can read a comment. Whereas stories is always a noun. Submission is the correct name for something submitted.
What I find more annoying is that it's on the right hand side even though all the other actions (vote on post, vote on comment, reply) are on the left hand side. Seems like a trivial thing but that is annoying quite a bit.
>>> 5. Find out which stories were the most popular on HN on a given day by visiting /front?day=yyyy-mm-dd. You'll see all the front page stories for that day, sorted by how much time they spent there. For example, Alan Kay's AMA had the most front page time on June 20: https://news.ycombinator.com/front?day=2016-06-20
That's cool, I guess, but algolia <https://hn.algolia.com/> seems like a much better tool for the task.
The one feature I can't believe I lived without that the HN Enhancement Suite chrome extension provides, is highlighting unread comments since your last visit. It actually makes it worthwhile revisiting e.g. a 200 comment thread when there are now 300 comments without just reading all the same comments again and being unable to spot the new ones.
If it became supported cross device by HN itself I would be very grateful.
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.
1. The time-capsule feature is really cool. Traveling back in time to see what sort of tech people were building / what other things were on the front page when X popular product launched is going to be so much fun. Update: it only goes back about a year and a half. See below.
2. Undoing votes has also been something I've wanted for a long time. I've accidentally downvoted/upvoted more times than I'd like to count when using my phone.
3. I currently use a bookmarking service to keep track of posts I want to save on HN, but native favoriting is much better. :)
Also, welcome, Scott!
--
Edit: I tried to view the front page [1] on the day I launched Breakup Notifier [2] ~5 years ago, but I get an error message. Is there any way you HN wizards can add the ability to go back further in time?
1. The up/down arrows after a vote leave behind a clickable void. That means you can still click that void after you have voted. If you changed the visibility on .votelinks instead of the buttons this would get fixed. Though even better UX would be to have togglable up/down buttons ala stackoverflow and others.
2. Why not provide the favourite link directly on the comment instead of forcing an extra click and page load. If it's a UI clutter issue maybe consider adding star and flag UNICODE characters. Again, having togglable icons for the same would be nice.
3. The collapse icon would be better off on the left for improved UI consistency.
EDIT: UNICODE characters don't show in comment. Is this a bug? They show in the textarea while composing the comment.
EDIT2: Add the following User CSS using your preferred browser addon for a bit of cleanup.
> 1. You can collapse comments in threads. If you're logged in, collapses persist across page refreshes and devices for a week.
The most impressive thing to me is that this feature exists and yet HN seems to have kept its good ol' fashioned <table>-layout. Obviously, it logically follows that it is perfectly possible to write a script to traverse a hierarchy of nested-<tables>, just as it's possible to recreate the Apollo guidance software in Brainfuck...but it's still impressive nonetheless.
If you collapse a comment in a thread it also collapses when viewing the comments page on a user's profile, and visually it is very hard to spot when collapsed on that page due to the styling.
For example, open the below link[0], collapse this comment, then refresh the link. The comment becomes quite hard to spot on that page. The red/orange star or vote button is also strangely missing while collapsed, which further makes it visually hard to distinguish.
Now visit your favs from your profile and you'll notice that "SQL Injection" post is automatically added your fav list. Just like upvote system fav needs to be protected against CSRF.
Well, that's true of collapsed comment threads as well, and I somehow doubt that logged-in users are the only ones who see things on the front page they'd rather not.
> why have all instances of "submissions" on HN been replaced with "stories"
Because posts to HN are either stories or comments? Happy to discuss this at [email protected] if you want to apply some lexicographical fine points.
That is a subtle point and I was curious if someone would ask about it!
Unvote links last for an hour. This is because the main use of voting data is to rank posts, and that's time sensitive. If we let people go back and unvote after hours have gone by (let alone years), that would be rewriting history, or counterfactually messing with it.
Even an hour is arguably too long. Since the main purpose of this feature is to correct misclicks and over-hasty impulses, a few minutes would probably be enough.
Collapses persist even if new comments are added underneath them, though the number of comments in the tree (e.g. '[+4]') will update.
Comments are submitted, too, though, so the word 'submission' seems oddly ambiguous to me. Also, I doubt I've ever anyone say 'submission' in conversation. People say "story" or "post" and of those two only "story" is unambiguous.
(But I'm happy to change it back if people feel strongly about this! It's an amusing lesson in how you can't change things without being noticed.)
yeah collapse is nice, but curious what will happen on collapsed thread which is added to...
i'm also confused, wasn't there already a "saved" section where upvoted items went previously? seems like all which was done was renamed a few items (and added the favorite which allows marking for later, without giving a vote)
The argument against that is that with the collapse button so close to the vote arrow, we would be guaranteed to get misvotes, especially on mobile. The undo vote feature would no doubt help with that some, but only so much.
I actually prefer it at the end, as HN uses the same (or very similar) theming for Desktop and Mobile. Before Reddit redid their mobile experience, having voting buttons next to collapse meant many inadvertent votes when trying to collapse on mobile.
Until HN has a good mobile theme by default, I'd prefer collapse and voting buttons to be well separated from one another.
The "pointer" cursor state remaining after clicking an up/down arrow looks like it was rushed or not quite finished.
I understand HN likes to keep things limited, which has been a real benefit to the overall UX on HN. But minimalism is often something that requires more time to get right, rather than just the result of having spent less time working on it. I feel like that might have been the issue here.
For me, at least, the most frequent use case for collapsing a thread is in the middle of it, when the discussion has veered off into territory in which I have no interest. In this case, I need to either scroll back up and find the originating post of the thread in order to collapse it, or scroll down until I find the beginning of the next thread.
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.
I agree this is somewhat confusing. If I collapse a comment thread on a story page, I wouldn't expect that same comment to appear collapsed in every other context. The only other ones that come to mind right now are: on a user's comments page or the new user's favorites page.
It would also be handy to have some visual guides for the indentation levels of nested comments as on Reddit. I've hacked my own indentation marks using a CSS injection for now, but this is clearly still not optimal:
I've also increased the size of the voting arrow because it's just uncomfortably small. By Fitt's law [0], smaller buttons require more time and effort to click!
A piece of kludgecode for Greasemonkey[Firefox] or TamperMonkey[Chrome/Chromium]. The script will all move the collapse links to the left margin on this page:
// ==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.
Re #2: yes, clutter (icons don't solve the clutter problem, and HN's design is emphatically textual), plus there should be a bit of a speed bump before favoriting much as there is before flagging.
Re: #3, I think when Reddit first implemented comment tree collapsing they also put the button on the right, but I saw a thread where someone pointed out that since the length of usernames is variable, putting the button on the left makes it impossible to mass collapse/uncollapse several comments by only moving the mouse vertically. After that they moved the collapse icon to the left, which I think is a much better UX.
Post explicitly emphasizes fairness in moderation with language 'shouldn't notice any changes in practice' and introduces moderator selected for merit and character ('meticulous eye for detail', 'thoroughly decent human being')
FW Ratio: 60%
Observable Facts
Post states 'you shouldn't notice any changes in practice' regarding moderation fairness
Moderator introduced as 'thoroughly decent human being' and 'excellent programmer'
Users can undo votes and unhide stories
Inferences
Careful emphasis on moderation continuity suggests commitment to equitable governance
Undo/unhide features provide users recourse against platform decisions
Post describes transparency about vote tracking ('you can tell which way you voted') and privacy controls (hidden stories persist only for user's own account for one week)
FW Ratio: 67%
Observable Facts
Users can see which way they voted after voting
Vote tracking appears only for that user via 'unvote' or 'undown' link
Hidden stories persist for one week per logged-in user
Comment collapses persist 'across page refreshes and devices for a week' when logged in
Inferences
Transparency about own vote choice respects user autonomy over their data
Post describes voting system that enables users to collectively valuate content and historical browsing that reveals collective priorities by showing stories sorted by 'time spent on front page'
FW Ratio: 60%
Observable Facts
Users can vote on stories (implicit from vote undo feature)
Historical front page browsing shows stories 'sorted by how much time they spent there'
Users can visit /front?day=yyyy-mm-dd to see front page stories for any date
Inferences
Voting system enables democratic participation in collective content valuation
Historical data reveals how user community collectively prioritizes content over time
Post emphasizes community standards through moderator introduction and describes governance structure enabling 'vacations and a day off' suggesting sustainable community service
FW Ratio: 60%
Observable Facts
Post introduces moderator and emphasizes 'shouldn't notice any changes in practice'
Structure described as enabling 'vacations and a day off' for moderators
Moderator described as 'thoroughly decent human being' emphasizing community values
Inferences
Moderation emphasis on community standards reflects community-oriented governance philosophy
Moderator team structure suggests commitment to sustainable community stewardship
Post does not explicitly invoke preamble themes but announces features that implicitly support human dignity through user agency and platform transparency
FW Ratio: 67%
Observable Facts
Post announces platform features and organizational changes
Moderator introduction emphasizes commitment to stable governance
Inferences
Feature announcements and governance clarity suggest commitment to sustainable human-centered platform
build 1ad9551+j7zs · deployed 2026-03-02 09:09 UTC · evaluated 2026-03-02 10:41:39 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.