What is the reason for posting this reply? I think I understand the sentiment -- it gets tiring to see something repeatedly. The reason I ask tho is it comes off as a bit dismissive, but I consider re-discussing a post every 1.5 years to not be too terrible, as: a) some people may have missed the first posting b) lots of new people can now get exposure and c) we have all changed a bit in that time and have new perspectives perhaps.
I know that discussion of stuff like this really helps people understand the material better, so I would personally prefer a bit of repeat on the good reads, to keep people up to speed than a keeping repeats to minimum.
I can also see another side -- this is to point people to previous discussions for the reason of them benefitting from what has already been said. I agree with this motive. I just think it would be better if there was a way to present it which has a bit less dismissive of a feel to it.
Anyway, I don't have a great solution in mind, more just exploring the idea. Cheers.
In short; I am attempting to be Constructive[1] and am using up-votes to guide my attempt.
----
[1]: http://xkcd.com/810/
a. Yes, it's tiring to see the same thing repeated. As a hacker, repetition, and hence wasting time, is something I try to avoid.
b. Yes, it's nice to present classic items to the newer members of the community. That's of value
c. Without reference to the previous discussions the same points will be made over and over again. See item (a) above.
d. There is value in the previous discussions. It would be a shame to see it wasted.
In short, I don't have a problem with things being reposted occasionally, but I'd like to leverage the existing backlog of discussions. Regarding sounding dismissive:
e. I don't have time to word-craft things endlessly, and sometimes I don't get the nuances right. It takes me almost no time to create the cross-references - the time is consumed in trying not to offend people. Sometimes there's not enough time for both.
I concur with this in general, but also suggest that repetition is a cornerstone of learning. Many ideas must be revisited several times before full understanding takes effect. This specific type of repetition is not wasteful repetition. It may not be you job to teach people, but I highly doubt getting in the way of others gaining understanding is your goal either.
e. I don't have time to word-craft things endlessly, and sometimes I don't get the nuances right. It takes me almost no time to create the cross-references - the time is consumed in trying not to offend people. Sometimes there's not enough time for both.
Fair enough. Seeing as how you are very frequently the person who posts the cross references (which btw, I really appreciate) I would like to propose this as a template for future "this is a repeat" posts (I certainly hope other jump in if there is a better way of putting it than my template):
This article is something of a classic here on HN. There have been some good discussions on it previously (see below). The comments in those articles may help provide some perspective for the discussion here.
$LINKS
If the repetition doesn't link to previous discussions, it definitely is wasteful.
It's like adding a comment without having at least skimmed through the already existing comments.
Since it is people who do the understanding, some repetition, while wasting bytes or words[1], certainly helps maximize reader comprehension. Even math and CS journal papers quote things, not just put pointers. That is wasteful repetition don't you think?
I look at it as an optimization problem. There are at least two variables -- number of words and reader comprehension[2]. The goal is information transfer between people. To minimize or maximize any one of those variables may result in non-optimal information transfer. Instead there may need to be some repetition rather than pointers for some things.
[1] There are serious questions at this point whether at the scale of HN discussions there is such a thing as limited resources for data storage, bandwidth, etc (and given the level of intellect here, even reading time is almost trivial for a lot of posts).
[2] There are lots of confounding variables, such as the intelligence and prior knowledge of any given reader, the eloquence of the writer, the complexity of the point being made etc.
No, that's not my assumption at all.
I find it very useful if someone summarizes previous stuff, or reformulates hard-to-understand (e.g. badly worded) previous comments.
However, you should do that consciously. There's no sense in writing a comment that essentially just repeats what others already have written in better words than you'd ever do. Doing that is a waste of time not only for you (the writer) but also for all the readers. And it happens a lot, simply because people are too lazy to skim though the previous discussion.
The above may be wastes of your time or energy or limited word count, but they are not wasteful to others (in fact, the opposite is true -- someone may actually be benefitting!). This is my point: what is wasteful to you may be beneficial to others.
You can downvote it, or wait until stories have been around for a bit so others will have sorted for you (and only read the top comments of course).
This is of course possible, and I don't object that as long as they know they are reiterating. However, this is only possible if people at least skim over previous posts, which is usually not the case, and which is why hints to previous discussions are not only helpful but necessary to avoid wasting time.
> This is my point: what is wasteful to you may be beneficial to others.
Repeating something for didactic reasons is sometimes indeed no waste of time for the writer. However, if the writer then publishes this, despite other people already wrote that stuff up in a much better way, that person wastes the time of the readers by filling up the comments with, let's face it and call it by its name, garbage.
Simple to implement; accumulated wisdom is not lost.
The presentation of previous discussions was as neutral, factual, and to-the-point as I can imagine; I don't see any dismissiveness or sentiment other than what I injected into it from my experience dealing with reposts on forums for a decade or so.
I see the RoG duplicate detection as serving the historian function you touched on admirably, without needing further padding in politeness.
There's only so much discussion, about discussion, a person can reasonably take :P
But it's the old usenet problem. FAQs I don't think would work here though.
I was thinking more as a collapsable "see also" section added only to duplicate articles.
Update Added reference to usenet.
Perhaps I'm trying to make HN something it isn't. Perhaps it would be better to consider it like twitter and simply ignore the past discussion and submissions. If that were the case I, for one, wouldn't hang around any longer, because the "new" stuff feels more and more just like the old stuff re-submitted or re-hashed.
Without back references I feel that people wouldn't be as keen to find genuinely new material. As it is, there seems to be more "news" than "hacker news".
That something hasn't been previously discussed is more a function of it being new, most of the time. I'd love to encourage people to post things which are not necessarily new but have never been discussed on HN...that'd be ideal. Otherwise, it's more likely that only time-sensitive items will truly be "new" in this sense to HN discussions.
What's a good example of "hacker news" vs. merely "news"?