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 -
The recent React code execution bug seems expose the current shallow reasoning behaviour of LLMs. So the react framework has had a serious security issue recently involving serialisation which apparently can cause arbitrary code execution. Some people have tried to generate exploits based on the patch using LLMs but this has failed. For example: https://github.com/ejpir/CVE-2025-55182-research/blob/main/TECHNICAL-ANALYSIS.md which assumes that the server would whitelist very unsafe modules for remote access (https://react2shell.com/). Of course the criticism of the LLM in the situation should be taken with a grain of salt because whoever is driving the LLM seems to have no idea what they are doing. It might be possible that someone who knows what they are doing is able to drive the LLM to a solution, but then question is how useful is the LLM. One advantage of the LLM in this situation is it allows someone with very little context of React and their bizzaro RPC protocols to quickly generate valid payloads that would generate weird behaviour and this could be used to generate a chain that would lead to code execution.
Without saying too much I'll say I've been part of an effort by my employer to use LLMs to identify security issues. They do a good job analyzing pieces of code in isolation for particular issues but a limited context window prevents them from finding end to end issues. For example, the LLM might flag that there's no input validation for function XYZ, but that's because the input validation happened much earlier in the scenario. Thinking about this the reverse way, generating exploits, probably means assuming that you've gotten the payload you want in the place where it will be parsed how you want which can often be the hard part.
As an aside Jesus Christ this is ugly code. I am very glad the brief time I spent working with Javascript was with Typescript.
More options
Context Copy link
This is just grifters and idiots who don't know how to code and got a claude pro subscription and think they can be the next great super hacker. In fact they are worse than the script kiddies of the old days.
You at least have to know about computer security in general as a concept to even be able to ask the ai the right question. But even if you do, eVen the best models have no shortage of hallucinations and lazy behavior.
More options
Context Copy link
More options
Context Copy link