Comment by password4321
11 hours ago
> duplicate discussion for the same link
I hate to be the bearer of bad news but this is incorrect per moderator dang at https://hn.algolia.com?query=author%3Adang+dupe&sort=byDate&...
Submissions of the same exact URL are automatically merged into the previous discussion server side, and are discouraged for about a year.
But one is a press release from ARM and the other is a report from CNBC. How are the two the same?
By your logic, there shouldn't be a gazillion posts about Apple Events the day it happens.
When the two submissions aren't the exact same link, it becomes a subjective question as to whether they're similar enough to count as a dupe or not. They aren't automatically always a dupe just because the overall general topic is the same, but nor are they automatically considered not a dupe just because they're not identical.
In this case the consensus (that I agree with) certainly seems to be that they're similar enough to be considered a dupe. Though that doesn't force the moderators to have to treat it like a dupe and merge comments.
Apple usually announces like 3-5 new products, each in a distinct market / audience fit. Arm announced one product for one customer.
But sometimes two long discussions ensue on separate days for one event/product/announcement, if it's big enough. Often the discussions are merged later on. No big deal.
And even for big news events (which, this might qualify as), people can miss the first discussion. Even if the discussions end up merged later on, the different discussions can still be fruitful.
Which is why, even if it is a duplicate conversation, the mods generally allow things to play out organically. There's either going to be more discussion above, or people have already said their peace and we move on.
It's not my logic, it's the logic of the moderator(s) of HN. Here's more, cut+paste from the link previously provided (https://news.ycombinator.com/item?id=43738815):
> I agree—they're not all the same story. On the other hand: stories in an ongoing sequence usually lead to repetitive discussion, which is bad for HN