Hacker News new | ask | show | jobs
by joseluisq 1875 days ago
If your affirmation is true, why many of HN users (me included) get [dupe] at first place? In general, Is not the HN intention to decrease number of duplicates? If not so then HN should provide a solution for prevent this, such prevention that is not happening today. Example search input.

Sorry but I'm seeing big contradictions in the so called rules.

Just one example:

> If a story has not had significant attention in the last year or so, a small number of reposts is ok. Otherwise we bury reposts as duplicates.

> "in the last year or so"

Not in the same month or even after some hours later.

> "a small number of reposts is ok"

Well, HN what to prevent duplications or not ?

> Dupes are not against the rules. You're likely getting downvoted by people aware of that.

With that premise in mind, let's continue making duplicate content. right?

So don't misunderstand me, since my intention here is just to put in evidence the same recurrent problem to improve HN. For instance I have also faced the same problem in the past so there is nothing agains rules or things like that, but instead is more a improvement for HN.

The reason because I'm interested on this is because I feel part of the community and this is a concern for me (I suppose for others too). Otherwise I could take the easy and dirty way to just say nothing and ignore the problem.

2 comments

The issue with duplicates isn't reposts of articles as such, it's not wanting significant duplicate discussions. We allow reposts as a way of mitigating the randomness of /newest. But once a story has gotten significant attention, we bury reposts as duplicates. (But after a year or so, enough time has gone by that a repost is ok again.)

In the current case, the previous submission didn't get much attention, so we didn't count this one as a dupe. In the case of your post https://news.ycombinator.com/item?id=26812145, the previous submission of the story did get a big discussion, so we marked the repost as a dupe. There's no contradiction.

Does that make sense? If not, take a look at some of the previous explanations. If you still have questions after that, let us know.

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

> > If a story has not had significant attention in the last year or so, a small number of reposts is ok. Otherwise we bury reposts as duplicates.

> > "in the last year or so"

> Not in the same month or even after some hours later.

A year is the expiration date on reposts of items that _have_ had significant discussion. Items which did not have significant discussion, and also did not have a large quantity of reposts already are exempt. In some cases the mods have reached out to submitters and suggested they repost items which the mods felt were interesting but did not catch on.

Unfortunately this is not clarifying my concerns about duplications in this particular case. I understand about the year of expiration and moderators can reach out submitters but for me is not clear what `significant discussion` means as well as `moderators could suggest submitters repost items which the mods felt were interesting but did not catch on`.

Essentially I still don't understand why some get label as duplicated and some others not.

Anyway, Unfortunately https://news.ycombinator.com/newsfaq.html is not clear at all for me and I think HN needs to make it more obvious to help members to understand without doubts or contradictions, which was the case for me.

So I will contact HN soon in order to request an account deletion.

Thanks for try to explain me about it.

PD. Sorry for the deviation of these comments from the main topic here. But I think my concern is already expressed on previous comments.