This is not a dupe of those 2 posts you provided. This post is about the update issued by Apple yesterday (those 2 posts are from 6 days ago) and is also a more broader discussion calling for Apple to release details of the bug.

Fair enough, Related... there's already a number of threads on the bug is the point. More discussion there.

Related doesn't meant dupe.

I agree with @lolinder that you are being overzealous about marking dupes. I understand the utility of preventing dupes but your behaviour is coming across as extremely bad faith here especially considering your top link is same as your last link and is pointing to a 5 day old post.

@dang Please look.

Yeah, @ChrisArchitect, you're often a bit overzealous about marking things as dupe. I hope that you weren't the one who flagged this off the front page, either, because this deserves to be seen and was making a lot more progress than the previous discussions before it suddenly fell off.

EDIT: I appreciate your attempt to clean up your comment in response to feedback, but your top link currently is the same as your bottom link, and even if it were correct it still only has either 2 or 1 comment depending on which of the two submissions by that title you meant to link to. That is well within the range of non-uptake that deserves a second chance.

nothing flagged

it 'fell off' because other things replaced it. Natural. Discussion still ongoing here. More discussion last week on a number of other threads, when it was news.

No, this wasn't natural. You may not have triggered it, maybe it was software, but I watched it rapidly rise from nothing to position #7 and then it dropped from #7 to #76 in 5 minutes. That's not natural churn, that was caused by user or software flags.

https://hnrankings.info/40433384/

Did you actually read the article, and my and lolinder's comments? Because this is different from last week.

Is it really that different though? There are now 5+ threads going on the same bug, with a lot of the same sentiments, repeating. Verge and some of these news sources aren't exactly on the ball with this stuff, it's just same news. There was a fix/update, 24 hrs ago, good. Whatever, moving on. The other threads provide some more of the insights people were sharing around the bug etc, more than what might be repeated here so far.

I think something you miss about the HN dynamic is that posts that fall off the front page quickly almost invariably have low-quality discussion compared to the ones that stay on the front page for longer.

Some of that is because low-quality discussions fall of the front page quickly, but most of it is because the first comments on a post are always low quality, because they're disproportionately from drive-by posters who read the title but not the article or the existing comments. If a post falls off the front page quickly, then those comments become the only ones that get seen, which means even if someone comes along with a more thoughtful comment (unlikely) it ends up buried with no upvotes and no replies.

If you let a "dupe" that's finally catching on stay on the front page for a while, the conversation invariably becomes better as the thoughtful commenters arrive and begin to leave their mark on the conversation.

In other words: just because 5 threads are ongoing and uninteresting doesn't mean that this one didn't stand a good chance of having a good, useful conversation if left alone.

Like I said, related doesn't meant dupe and this is different from those posts. When Apple's CSAM thing happened, we had multiple related posts too but they weren't dupes.

I won't respond further because I don't want this turning into a flame war.

Please stop with the [dupe] comments. No one is asking you to do it, and you’re not doing a good job of it.