So I log into HN and read the wonderful essay about healthcare and end-of-life costs. I was going to comment and vote on some of the comments, but I can't downvote.
Must have ticked somebody off, I guess.
I upvote a few of the better comments and move on.
Then I go and read about the new Chrome HN extensions. Nice job!
Now I can upvote and downvote.
I go back to the healthcare essay. Still no ability to downvote.
Does anybody here besides the coders of HN want to support the idea that the user can have abilities come and go on a whim and this is going to make for a enjoyable user experience? HN keeps getting more and more nuanced about who can do what when, and, quite frankly, all it seems to do is intermittently piss me off. If it's making things better I can't see it. And even if it is, you don't screw around with system behavior without notifying your user of what's going on.
I'm sure somebody will point me to some thread somewhere or another where pg explains that for condition X we're not allowing users to downvote. And also frankly, that's part of the problem. Understanding the system shouldn't require extreme devotion to every little thing said about it over a period of years on every thread related to HN. A system should be simple to use and understand. HN is still simple to use, but beats me if I can understand it any more.
So am I out here all alone in this feeling, or is it bothering other HNer's as well?
Lines 1095-1098 control whether the downvote arrow is displayed or not.
So, to answer your question, yes, it bothers me that there's very rarely a clear enumeration or description of features.
On the other hand, it's been a wonderful opportunity to learn Arc.
(I'm only half joking - Arc was actually my first stab at functional programming and I probably wouldn't have tried it if pg had bothered to document HN's features)