Hacker News new | past | comments | ask | show | jobs | submit login

The reason is that it's not really what users want

Yeah, actually, it is. Seriously.

Nothing makes "hackers" look worse than a hack that doesn't work.




The true hacker solves the right problem. Expired links are just the visible problem. The real problems are more subtle: users voting up fluff posts, nastiness in comment threads...


If one clicks next to go beyond the first page repeatedly, there is effectively a timeout how much time can be spend until the link expires and one has to start from the beginning.

I think this makes it more tempting to upvote something just after looking at the headline instead of after reading it, because one has to remember so much or use so many tabs or bear with going back to the front page and clicking next again.

I have no idea about everone's behaviour, but maybe expired links in the end also affect something like users voting up fluff posts?


Do you really think you can't solve both problems, or that fixing links hurts your ability to solve bigger problems? It's $500 to a contractor. You can even have someone else find the contractor. This smells fishy.

I suspect the fix will result in a large change to the code base and you want to always own/understand the code for some reason. So if you can't fix it yourself, nobody is allowed to, either. That's fine--just admit it's your baby and you don't want to let it go.


I guess it's also because of the technical elegance of using closurees for page actions. It's hard to admit that a technique that feels elegant and expressive fundamentally doesn't scale.


That's part of being a mature developer. We've all stood stubbornly by a piece of inappropriate code that we want to use because it's so clean and elegant, but most of us have gotten past that stage of ego development by the second or third year of school or professional life. It goes without saying that Paul Graham has long since transcended that level.

So, the only answer that fits all of the parameters is that he's trolling us.


Or that it's not his priority - that's the stated reason.


Not buying it. Priority or not, who leaves a forehead-slapper like that in their code for several years?


You're not far off to assume it hijacks your thinking process and steers it to the unimportant.

The change to the code base would be easy. You can increase the expiration timeout or keep around more closures. It would come at the expense of using more computer hardware, which is an elegant technique of scaling: you free your human hardware to work on more important things.


When a fluff post gets posted some users flag it and some users upvote it.

Is there anyway to penalise the people upvoting a fluff link? Mods have a 'fluff link' flag, and using that applies some karma loss to everyone who upvoted the post and puts a notice on their user page? (This is an ugly kludge. It's meant as a thought experiment rather than a serious implementation idea).

I have made some comments on HN which should have been heavily downvoted but which got no downvotes or even upvotes. I have no idea how this can be fixed.

Some people on HN have an aversion to down voting and flagging and will only use these tools for the most egrarious examples of bad posts. It would be good if people accepted getting and giving downvotes as a useful tool in running the site.

There's another problem with people responding to people who are effectively trolls rather than ignoring or downvoting those posts. I know there are few moderators with very little time. More mods is not the answer, but perhaps 'big downvotes' for those mods would help. Applying a -5 or -10 downvote to people posting aggressive dumb comments would help set tone.

Perhaps having links to all the guidelines (including the links provided to new users) under the submission box would be useful?


My main problem with the "More" button is that it doesn't always give you more. I suggest a text change on the anchor tag to "More, if you're quick about it", and the error message to "You weren't quick enough."

This way I can only blame myself when pressing the button doesn't work as expected.


There is so much more educational value in this conversation than just people saying "serve your users but question what they say they want", as it is right in the action - with all its nuances.

Great lesson on prioritization!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: