Live data from Hacker News

Coming Soon to Hacker News: Pending Comments

news.ycombinator.com

471–480 of 854 posts

Re: Coming Soon to Hacker News: Pending Comments

#471
post #329

Earlier quoted context omitted.

Let's see how much of a problem there is first. I wanted to start with the simplest possible thing. If it breaks in some cases I'll add stuff to fix those.

An additional suggestion- don't show username on pending comments. Let the comments get approved solely on their own merit. That should cut out a lot of concern about a ol' boys club, and honestly should do a lot to improve comment quality as well.

This is a very important consideration.

Re: Coming Soon to Hacker News: Pending Comments

#472
I think this is an interesting solution to a common problem. The problem isn't poor comments, it's how to deal with a community site when it's in the post-early adopter phase. In the past, when sites like this hit a certain maturity level, you have a few problems: people complain about all the new users and the loss of character. It's all part of what happens when network effects take hold and your site has an increasing number of users. Once you've hit a certain inflection point, each site evolves whether they want it to or not...

I think Slashdot ignored it and lost a lot of relevance to Digg. Digg tried to pivot to be more marketable and drove people to Reddit. Reddit hit that point and decided to fracture into lots of sub-reddits (which I think was the most successful way to evolve so far). [1]

The pg/HN approach is basically to leave it to the users who've been around longest to cultivate the community. It's a lot of trust to put into those 1K+ users, but probably not overly so. It remains to be seen if this can be a successful way to keep HN relevant to more than just the YC-set, but we'll just have to wait and see. Hopefully this works out better than Slashdot meta-moderation (which was just odd).

[1] This is my take on the histories of these sites... they all went through the growth, plateau, and loss phases to some extent. I'm sure others can tell me if earlier communities had the same patterns.

Re: Coming Soon to Hacker News: Pending Comments

#473
post #321

Earlier quoted context omitted.

This was all the code it took: (newsop pending () (pending-page user)) (newscache pending-page user 60 (listpage user (msec) comments* [if (and (cansee user _) _!pending) _] "pending" "Pending Comments" "pending" nil)) In this project I've really benefited from having kept the code tight.

Forgive me for asking what's probably a simple question: what's HN coded in? That's pretty clearly a flavor of Lisp... what's the square bracket predicate syntax?

IIRC, it's written in Arc

http://arclanguage.org

Re: Coming Soon to Hacker News: Pending Comments

#474
pg - I am going to reply to this (even though I fear it might cause me to never be able to post another live comment again)

It seems to me that your aim is to trying to protect the people reading the comments, but this will only protect the people whose Karma is less than 1000! That is to say, it actually protects the people who use the site the least, and in response to what, those people "diluting" the site? Presumably the others who have 1000 Karma earned it by making enough good posts and comments. So you are protecting the wrong group!

Reddit allows people to see highly nested comments by explicitly clicking a link. Here you would be completely hiding them from anyone except the HN "regulars". It seems this will only decrease value for those people. Why not give them the OPTION to see those comments by clicking a link to expand, like on Reddit?

And what if I delete a pending comment after a couple days, does it reset this status - which is like a hellban but only with regard to visibility to lower-karma users? Also what happens to replies to a pending comment?

Requiring too many people to vote and participate in site governance (and given the number of comments, this will require a lot of HNers with high karma to keep being active) often doesn't work. Consider when facebook asked its members to vote - it didn't receive enough "turnout":

https://www.facebook.com/notes/facebook-site-governance/resu...

Thus until you get this system to a point where it's good enough, I strongly suggest you give everyone the OPTION of seeing "pending" comments. Or at the very least, make the pending comments grayed out so that high-karma HNers would be psychologically conditioned to click on them to endorse them (and subsequently click again to un-endorse them).

Re: Coming Soon to Hacker News: Pending Comments

#475
post #112

Earlier quoted context omitted.

That might work... but only if people actually read that page. Given how few people look at /newest (as estimated by the fraction of votes which are cast before submissions hit the frontpage) I'm not optimistic. How about only placing comments into the "pending" purgatory if the submission they're attached to has received more than X comments in the past Y minutes? I assume it's the chatty discussions which you're co…

I think I like this idea quite a bit. I don't know how many users there are with >1000 karma, but will they be motivated to keep endorsing everyone else's pending posts? Sometimes good discussions do happen on quieter threads, or way down the list that the 1000+ users might not see. Well, I guess it really comes down to just how much (proper) endorsing ends up happening. One thing I like about HN is that it's open an…

Well, hopefully new users can hit the 1000+ mark quick enough to not have it affect them too much.

But, I wonder how the lack of visible scores on comments has affected the overall comment scoring rate. For the average new user today, how long do they have to wait to get to 1000 karma? How long was it a few years ago? These would be interesting questions to answer.

Re: Coming Soon to Hacker News: Pending Comments

#476
It's unusual how intolerant of experimentation entrepreneurs can be.

This may or may not work. PG even acknowledges that it's likely to go wrong initially. Implicit in that is that they will work on fixing it until it's working better than the current system. In the end, it's guaranteed to either completely fail as an experiment (they'd probably roll it all back) or yield something working better. Yet there's so much angst about the changes here.

It's not always irrational to get concerned about changes. For example, laws are typically written and then there are substantial barriers to revisiting them. In the case of a website, though, why worry? If this isn't working better, it's extremely unlikely that YC would leave it in that state.

Re: Coming Soon to Hacker News: Pending Comments

#478

This is ridiculous. It's bad enough that people are downvoted for contrarian opinions, but now our comments need to be vetted by the elite HN users before they can be shown to the rest. I don't get it. This site looks like something made in 1996 (with absolutely no regard for readability), but the big new upgrade we're getting is a draconian (and wholly unnecessary) comment moderation feature/policy? A lot of HN user…

I would endorse it, because I think you're mostly right, but then i'm probably part of the problem and not the solution. Even if I disagreed with you I would endorse you because I think a too-well tended garden all too quickly becomes a tomb.

Re: Coming Soon to Hacker News: Pending Comments

#479
It's hard to tell how much friction HN needs. Some more, probably. A lot more? I'm guessing not. A little moderation goes a long way.

Metrics for comment approval might include opening up a thread complete, or for folks with a karma threshold, or who have made posts in the past without being downvoted much. (The _Making Light_ site has some interesting ideas here).

You might include who voted on an article, and how. If someone's gonna moderate, they may as well be listed as having moderated (so they can get the credit or blame). Meta-moderation might be one of the things that killed Slashdot, though.

Re: Coming Soon to Hacker News: Pending Comments

#480
post #321

Earlier quoted context omitted.

This was all the code it took: (newsop pending () (pending-page user)) (newscache pending-page user 60 (listpage user (msec) comments* [if (and (cansee user _) _!pending) _] "pending" "Pending Comments" "pending" nil)) In this project I've really benefited from having kept the code tight.

Forgive me for asking what's probably a simple question: what's HN coded in? That's pretty clearly a flavor of Lisp... what's the square bracket predicate syntax?

It's written in Arc.

Regarding the square bracket syntax:

    [... _ ...]  is an abbreviation for (fn (_) (... _ ...))
http://www.paulgraham.com/arc.html

http://en.wikipedia.org/wiki/Arc_%28programming_language%29

Post reply on HN