4 ms·
Thank you, I am very much familiar with the site guidelines. GitHub's Trending page has previously featured many similar projects, open letters and other non-s
by hmyr0 8y ago
Thank you, I am very much familiar with the site guidelines.
GitHub's Trending page has previously featured many similar projects, open letters and other non-software repositories, so I don't see how this is relevant here.
I understand that not all readers are interested in or even affected by GitHub's acquisition; however, a large number of them are. For this reason, a downvote button would be significantly more effective and democratic than giving two or three users the ability to completely hide a popular submission they do not agree with.
I do believe that dang and the Hacker News moderators have developed a good sense of how to keep the community healthy. Unfortunately, the most reliable way of accomplishing this is to eliminate any and all controversy that could lead to debates and arguments. This, however, is not indicative of a good community, it simply places users in a filter bubble by only showing them content that no two other users have ever disagreed with.
Despite eliminating nearly all arguments and controversy, this nonlinear voting mechanism is dangerous to the community and society as a whole, even if it gives the impression of a healthy community. Removing controversial submissions just as quickly as spam, child pornography and incitement to violence as can be expected from oppressive regimes is not an indicator of a healthy community, but rather that of a community that only gets to see what everyone agrees with.
Many people who have spent much more time on Hacker News than I have agree that there is room for improvement (see, for example, the analysis from last year that I linked to above). Unfortunately, simply hiding all controversial submissions saves the moderators time, and it seems that they are currently not interested in investing additional time into creating a truly healthy community, one that is capable of remaining healthy despite openly holding and expressing different opinions, and thus the current form of moderation is likely going to remain as it is now.
- tomhoward 8y ago> "I understand that not all readers are interested in or even affected by GitHub's acquisition" Most people on HN are interested and affected, which is why it's been discussed so much in the past week [1]. Few if any stories have been so heavily discussed in all of HN's history. > "giving two or three users the ability to completely hide a popular submission they do not agree with" > "it simply places users in a filter bubble by only showing them content that no two other users have ever disagreed with" If that was actually how the site worked, top users would mutiny, the whole community would depart, and then dang would lose his job as there'd be no community left for him to moderate. > "eliminating nearly all arguments and controversy" > "Removing controversial submissions just as quickly as spam" There's disagreement and controversy on HN all the time. HN is not controversy-averse, it's averse to stories that lack originality and substance. > "Many people who have spent much more time on Hacker News than I have agree that there is room for improvement (see, for example, the analysis from last year" Sure. I agree there is room for improvement. Dang agrees there is room for improvement. You'll note that dang participated actively in the discussion thread about that post, and even helped with the writing of it by providing clarifications. > "it seems that they are currently not interested in investing additional time into creating a truly healthy community" Dang spends all day every day (including most weekends) working to make this community healthy, which includes reading and considering all the feedback that comes his way. He does this like his livelihood depends on it, because it does; if HN declines, he's out of a job. It really does seem like your critiques are based on misapprehensions. It's good that you're so passionate about helping to make HN better, but you'll be more effective at that if you spend some time properly understanding it :) Anyway, I've said all I have to say so I think we're done here. [1] https://hn.algolia.com/?sort=byPopularity&prefix&page=0&dateRange=pastWeek&type=story&authorText=false&query=github https://hn.algolia.com/?sort=byPopularity&prefix&page=0&date...