This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

Jump in the discussion.
No email address required.
Notes -
Grand Theft Crypto, Episode LXXVI
New week is here, time for new culture war happening is here. Maybe it belongs to finance thread, but both cryptocurrency and cryptocrime are now inseparable part of our culture.
Coldcard Hardware Wallet Flaw Linked to $70 Million Bitcoin Theft in 41 Minutes
Yes, safe crypto technology had proven to be unsafe once again. Follow the links in the article for more nerd details.
Why is this important? This time, this not due any fault or slip at the user side - their only mistake was trusting the professionals of Coinkite business operating since 2013 and considered one of the best by everyone in crypto.
Bitcoin is not to blame, Bitcoin worked as intended. The random numbers generated by Coldcard were not random.
Little parable for non nerds to grok what is it all about:
Now, what are lessons of the episode?
1/ Another proof that crypto hadn't brought world peace and harmony as some more devoted fans promised, but crypto made crime cool again. Grisly, retarded and boring ordinary everyday crime stays, but evil genius was conjured from pages of pulp novels to reality.
2/ Trust no one. If you want to make you crypto stash really secure, you need to make your own random number generator, this means using the gold standard of physics, radioactive decay. No randomer random events can be found in this universe.
Too much work? Say good bye to crypto and invest in white powder. What you put in your nose, no one can take away from you ever again.
edit: links
Here is a linkedin-free writeup. Low entropy key generation is an oldie but a goodie -- I recall when ssh keys generated with Debian had this problem.
For this particular story, I think that the morale is that rather than worrying about increasingly far-fetched modes of attack ("yes, you can keep your key on an airgapped encrypted OpenBSD laptop, but what if someone steals that laptop and manages to brute force the passphrase, would you not prefer some hardware encryption where the chip clears itself after three wrong passphrase entries?"), you should worry about "what if my niche crypto implementation is not as secure as anticipated?"
Also, if you make hardware wallets, auditing that the crypto is implemented correctly seems to be (not to put too fine a point to it) THE ONE JOB YOU HAD? Most failing cryptography fails not because the math is unsound, nor because someone has a quantum computer with sufficient memory, but simply because implementations are hard and people write buggy code. I know enough about crypto to not try to roll out my own implementations. "Key generated from low entropy PRNG" is a failure mode we had before. I recall Truecrypt simply prompting you to type a lot of noise simply because they did not wholly trust their supposed hardware randomness sources.
The #ifndef vs #if thing is likewise fun -- sure, usually it is not that harmful.
I will go out on a limb and say that this seems exactly the kind of bug an enterprising cybercriminal would discover with the help of an unfettered LLM these days. Being a hardware wallet where all the paranoid people park their coins makes it a juicy target, of course.
Someone did point out this vulnerability was discovered shortly after one frontier model or another was released. But then again, there are new models every day, so who knows.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link