News for hackers. Stuff that matters.
Re:Hacker News bans Google and all other search engines by qeorge on Monday March 15, 2010 @07:57PM (#1194500)
That's probably the main issue. HN's authority and DoFollow'd links make it a prime target for linkspam.

There's a lot of reasons I'm bummed about this, but I have to say: startups missing out on free PageRank is not one of them.

Re:Hacker News bans Google and all other search engines by pierrefar on Monday March 15, 2010 @08:33PM (#1194575)
The way it's done now is that all new submissions are nofollowed until they hit a certain karma threshold. A while back when I looked at this, the threhold was about 3-5 up votes.

This is actually a very neat and simple way to exercise editorial control to remove the nofollow: if enough people in the community like it, there is something useful about it and it is vetted.

Re:Hacker News bans Google and all other search engines by ericb on Monday March 15, 2010 @08:00PM (#1194505)
The links are nofollow'd now.

edit: Oh wait, seems that only comment links are nofollow'd.

Re:Hacker News bans Google and all other search engines by weaksauce on Monday March 15, 2010 @08:05PM (#1194515)
Actually some of the links are nofollowed until it hits a karma threshold. Not sure of the value but it seems that a story with >50 votes is not currently nofollowed.
Re:Hacker News bans Google and all other search engines by new_account on Monday March 15, 2010 @09:05PM (#1194624)
It seems that a lot is going on - in secret. Example: I just discovered that if I reload the page my votes for comments get rolled back.
Re:Hacker News bans Google and all other search engines by blasdel on Monday March 15, 2010 @09:33PM (#1194664)
It wasn't rolled back: it was never counted.

There's a disenfranchisement heuristic that causes your votes to be recorded (can't vote again) but not counted. It usually persists for about a day. I think it's supposed to kill voting rings but its behavior is pretty odd.

The number in your browser gets incremented or decremented client-side independently of reality — it's doing a blind GET request by pre-fetching an 'image', not making an XHR POST and getting the new karma value in the response. Like a lot of things in Arc, it's just poor HTTP.