4 ms·
How can we possibly have a duplicate discussion about two different contexts? One is a first party announcement, the other is a third party news article explain
by aspenmayer 2y ago
How can we possibly have a duplicate discussion about two different contexts? One is a first party announcement, the other is a third party news article explaining and contextualizing the first party announcement. Often, third party news articles include direct quotes from relaxant first party sources that are not present in the first party source, and may not be present anywhere else. So I don’t see how the discussion would necessarily be duplicated either.
Do what you want, but it’s not a duplicate submission by definition, and isn’t necessarily a duplicate discussion. This is a place to comment on the specific article I posted. That distinction seems clear to me.
I’ve had this discussion with dang before, and due to our conversations, he has planned karma sharing among related and even explicitly duplicative submissions, because reposts happen, and for some topics, to limit all of HN’s discussion of a given topic to a specific post’s context is unreasonable.
We both have the same goal here - to connect people with relevant information. There is an actual dupe problem on HN, but alternate sources of information does not a dupe make.
- ChrisArchitect 2y agoIt's only a few hours after the initial release, it references the release, it doesn't add much more to the release. So share it over there, where the discussion is happening. Could have a whole thread in there about this article if you want. Otherwise we'll have two discussions on the same topic with everyone repeating themselves? The news story in this case is the release, which was posted earlier, and is being discussed. Hence "more discussion on official release". Why are you forcing me to see 10 posts on the same topic? (as this probably won't be the first dupe submission) Reposts happen, but weeks/months later perhaps, not hours. Not trying to limit the discussion but keep it in the same place, to avoid the duplicate post and threads.
- aspenmayer 2y agoThese are fine preferences to have, and I don’t disagree one bit. I agree that in this particular case, a thread on the first post would also be appropriate. People have different reasons for posting than you do, and many/most are valid/compatible with HN guidelines. Your goals of centralizing discussion I tend to agree with, but I’m making a broader comment than this specific submission. There are perfectly valid reasons to prefer to make a point on a submission with fewer comments than one with many comments, especially if one hopes to not have their signal lost in the noise. No one is forcing you to post these dupe notifications, and I actually really appreciate that you do. I just mostly take ire with calling them dupes when they’re not an exact URL match or redirect, because the word dupe in the context of discussion boards has a highly specific meaning to me that predates my usage of HN, and also the existence of HN, and even web forums. Not that it matters in the context of HN, I just find it slightly grating and would prefer that other instances be called “related” posts or something, but I don’t necessarily think you should change your behavior. I don’t know why I am like this, and I can see how it is a silly thing to care about, and minor quibbling point besides. But hopefully that helps you understand why I find my good faith posts being dismissed or labeled as dupes when they’re not dupes frustrating. I also understand your usage of them being duplicate discussions, I just don’t think that’s really a problem on HN at all compared to actual duplicate exact URL match submissions. Please do keep posting your dupe link notices though, whatever you call them lol