zlacker

[return to "Hacker News Guidelines"]
1. yjftsj+3c[view] [source] 2023-08-24 17:09:22
>>tonmoy+(OP)
The one thing I wish was added - either in the guidelines or as a change to the actual web UI - was replying to a comment that you're downvoting; it's frustrating both to have one's own comments downvoted without explanation, and to come across a comment that's grey without obvious reason (Was it factually incorrect? Endorsing an unpopular idea? It's not always obvious).

(I'm not saying HN should do exactly the same thing, but one example is Slashdot's system where a comment can get downvoted in a way that tags it specifically as trolling/offtopic/whatever - https://slashdot.org/faq/mod-metamod.shtml seems to describe it alright)

◧◩
2. jedber+wd[view] [source] 2023-08-24 17:14:07
>>yjftsj+3c
It's an interesting idea, but you'd end up with a situation where the worse the comment, the more discussion it generates due to the forced replies, which is sort of the opposite of what you want.
◧◩◪
3. yjftsj+de[view] [source] 2023-08-24 17:17:32
>>jedber+wd
Perhaps a system where a comment can only be downvoted if it has at least one reply? So someone has to explain, but only once
◧◩◪◨
4. pvg+ZC[view] [source] 2023-08-24 19:11:38
>>yjftsj+de
It has the exact same problem as the original idea - its motivation and purpose is really reducing the personal sting of getting downvoted, not 'producing an interesting set of comments ordered by some approximation of interestingness'. Notice how nobody ever suggests or advocates for 'receipts for upvotes'.

It's a totally sane motivation it just doesn't obviously make a messageboard better.

[go to top]