309 karma · joined August 19, 2022
US: "we demand the right to spy on anyone for any reason, except US citizens where we absolutely must recognize their constitutional rights"
EU: "we demand basic protections for the rights of our citizens"
And for a small open source project, a 500€ fine is enough to make development and publication unattractive, a percentage of a devs yearly income is painful, and tens of thousands of Euros would be dangerous to the long-term financial well-being of the developers. Even if the fines are a lot lower than 15M€, this proposal stays shit as written.
That is a very rose-tinted view of EU regulators. Europeans are people like everywhere else on the planet, we're not somehow immune to regulatory capture (though I feel it might help the institutions that we haven't yet powerful blocs like the GOP that set out to destroy any kind of regulation in order to prove it's infeasible). Heck, German industry giants are practically married to the state here, there's absolutely no fucking way a company like VW or Opel will go under if a rich government like Germany can do anything about it.
More to the point, the author themself is pro-CRA for a range of things that seem to have purely positive effects, as they spell out quite clearly in the article. The points brought up are nevertheless important: we shouldn't be okay with legislator making objectively shitty laws devoid of any technical comprehension or economical realism and hope it'll kinda be fine when the bureaucracy and courts actually implement it. Just having the danger of having to pay 15M€ for my open source project because it might be used commercially is a horrendous imposition.
Everyone here seems to forget that we regulate these industries so finely because they are in a uniquely dangerous position to harm people, and act as if this is a blanket statement that's true for any kind of software development. This is most definitely not true, and we should think hard and long before regulating a thriving industry out of the world in order to feel superior to all those rubes over there obviously doing it wrong.
Regulation is a necessary evil, not a positive good in itself.
Also, nothing about compliance is actually about "consolidating security debt" or "quick decisions". It's about paying someone to go through checklists and, like a reviewer of a scientific paper, find something, anything, no matter how inane, to criticize, before handing you a certification. Any slightly unconventional new idea to improve security in your product will be suffocated beneath the blanket of compliance.
> I'm totally rooting for this because its the only thing that will improve security.
So does the author. Well, they strongly endorse a sensible version without the vague phrases and open-source-killing blanket statements, and without brain-dead sentences like "your product must be un-DDoS-able". I do wonder, though, why you're rooting for legislation that would kill any open source project that might, conceivably, be used in a commercial setting?
Because the US has, in the past decades, not waged a war against a near-equal opponent who could have held together any kind of air force or air defenses for at most the first few days of a US invasion. In all of the US wars since the A-10 might have been obsolete against a near-equal opponent, it was more advanced than the mass of opposing tech, and could be used well. For counterinsurgency, the cost of actually modern tech is more of a problem, given that the cheap old stuff is still far superior to anything a Taliban commander can put in the field, and given that guerilla warfare has as it's aim not tactical victories, but increasing the cost to the bigger party into politically untenable regions.
It is very much obsolete in the sense that the US also requires air capabilities for large, near-equal conflicts, and there is no unsurprising way for A-10s to be useful there. In summary: keep enough A-10s around for CAS against outclassed opponents, but don't plan on having enough to take on China, seems like a wise strategy.
Each day, it went the same: sit down, try to write about the work, find some meta problem to occupy myself (like "is this the correct order of topics that I'm planning to write in my outline" or "under which topic does this idea belong") before actually writing about the thing itself, cue an unproductive spiral of research into these distractions. After a couple of hours of not actually doing any progress, drift off into the internet "as a break", and only come back to the thesis for 20-30 minute intervals that are exactly as useless as they sound. Become more and more frustrated, but no more productive, as time goes on.
Vomit drafting suddenly gave me a productive focus. Suddenly it was clear that yes, where I want to put this topic is good enough, or there is this one other place where it makes a lot more sense. No more long internal debates over meta-questions. And I realized that yes, I do have a wide range of knowledge about my specialty, something I'm convinced I was subconsciously blocking on before ("what do I do if I try to write about this topic but realize I'm just too stupid to get it, and was just bluffing all the time?").
Entirely untrue.
Peer review is also obviously a bad solution for the reproducibility problem, given that we've got the problem now, concurrent with generations of peer reviewed manuscripts.
And we nevertheless pay the price of adhering closer to orthodoxy for it, since effort being put in is a rather superficial "this paper sounds reasonable to me" filter, perhaps with some boxes that must be checked like p-value or sample size.
So "peer review" isn't holding back kook theories at all on its own. At best, journal prestige is bolstered by it, which the journal can then translate into holding them back. The track record is a bit unclear, though.
This article mentions Einstein being offended that his paper was submitted to peer review by Physical Review, and submitting it elsewhere instead:
"We (Mr. Rosen and I) had sent you our manuscript for publication and had not authorised you to show it to specialists before it is printed. I see no reason to address the – in any case erroneous – comments of your anonymous expert. On the basis of this incident I prefer to publish the paper elsewhere."
I just recently ended up there via this blog: https://experimentalhistory.substack.com/p/the-rise-and-fall...
which argues, not unconvincingly IMO, that peer review is a failed experiment which tries to stop bad science at the price of also stopping brilliant, unconventional science, where instead we would profit more from letting the scientific public do the sorting instead of hand-picked specialists. The author phrases it as science being as strong as its strongest links, not as weak as the weakest one, and we should do everything to get the brilliant crazy ideas.
Of course, "We want this code to run forever the way it is" is a value option that a company can choose - just not with any language it wants. And somehow, people seem a bit reluctant to switch from Python to C to be able to keep running the same programs forever, guaranteed.
That is a lot worse than formatting squabbles, especially for a glue language where you are expected to be able to copy snippets for short scripts all the time.
In addition, anything making MAD impossible will have very, very far reaching consequences for world politics, many of which are offensive. Any state that can unilaterally deploy nukes without fear of reprisal is on it's way to the total global tyranny you mention.
And it's shit, because unilaterally declaring you're not gonna do it won't work at all, so there needs to be enough trust between the parties to institute a supervision regime, otherwise, if something is technological possible and promises military benefits, it will be done sooner rather than later.
You did read the little sentences under the big bullet points, right? It's "first, let's see if it's smarter to not do the work at all, before we commit to automating", not "don't automate the boring stuff"
She actually tweeted back both of them asking for details, a level of understanding neither tweet actually merited (but still a good strategy), and got no answer.
There, now you won't even need to read TFA :)