News for hackers. Stuff that matters.
[dead]
Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by stouset on Monday June 24, 2024 @07:26PM (#40782282)
Downvoting isn’t censorship. It’s disagreement.

“What about this one C project that hasn’t been a mess of exploitable vulnerabilities” is thoroughly unconvincing in a world where networked C programs are an unending source of severe vulnerabilities.

Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by VancouverMan on Monday June 24, 2024 @08:08PM (#40782672)
When even a very small number of downvotes here can result in a comment's text being coloured in a way that makes it harder to read, or even nearly impossible to read in extreme cases, I think it's reasonable to equate downvoting with censorship.

Censorship doesn't require content to be completely hidden or blocked; even just partially obscuring the content in some way is still censorship.

Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by stouset on Monday June 24, 2024 @08:46PM (#40782985)
I disagree that this is equivalent to censorship, but it sure sounds like a really good incentive to make more convincing comments than “Then how do you explain this single counterexample? Checkmate, Rustaceans.”

Plenty of reasonable disagreement happens here without getting downvoted into obscurity. Substantive points are generally upvoted even when they’re controversial opinions. So I don’t feel too upset when borderline-trolling or bad-faith arguments get hidden by consensus.

Ironic counterexample: It looks like you may have gotten downvoted despite having a fundamentally reasonable perspective.

Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by kelnos on Monday June 24, 2024 @11:22PM (#40784103)
I wouldn't call it "censorship", but sure, let's say it is.

There's a reason why "this is the exception that proves the rule" is a common saying. Picking out one exceptional example of something, and using that to argue against a general point, is at best lazy, and at worst actively dishonest. I'm fine with those kinds of comments being "censored". They -- and the comments calling people out for doing this -- are boring and don't further discussion.

Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by kelnos on Monday June 24, 2024 @11:22PM (#40784104)
I wouldn't call it "censorship", but sure, let's say it is.

There's a reason why "this is the exception that proves the rule" is a common saying. Picking out one exceptional example of something, and using that to argue against a general point, is at best lazy, and at worst actively dishonest. I'm fine with those kinds of comments being "censored". They -- and their replies that call people out for doing this -- are boring and don't further discussion.

Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by devwastaken on Monday June 24, 2024 @07:10PM (#40782137)
It's not censorship to be downvoted for low quality posts. Please reference "intellectual honesty" and research how to have legitimate conversations. Reddit/Twitter/4chan esque communication is not appropriate for serious spaces.
Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by lasjhdh on Monday June 24, 2024 @07:15PM (#40782183)
Intellectual honesty would be to point out the memory safety issue CVE of Postfix in the past decade. Which you studiously avoid. But in any Rust thread cult-like obedience without questioning is expected.
Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by dmix on Monday June 24, 2024 @07:32PM (#40782340)
> Intellectual honesty would be to point out the memory safety issue CVE of Postfix in the past decade.

this thread isn't about Postfix, you brought up Postfix as a counterpoint to a wider topic where such a anecdote doesn't hold up nearly as well in a broader scope. Don't purposefully narrow the topic and move goalposts just to win internet fights.

Re:More Memory Safety for Let's Encrypt: Deploying ntpd-rs by dequan on Monday June 24, 2024 @07:50PM (#40782518)
What an interesting coincidence that all three of these accounts were created within 15 minutes of each other. I'm sure all "three" users are being "intellectually honest" here.