Earlier quoted context omitted.
I find a lot of the inefficiency also comes from the model just randomly poking around and grepping all the time which is the fault of the harness. I ended up building a Prolog based MCP where I use tree-sitter to parse the code into a graph, and then the model can just ask questions like 'what are all the functions connected to this function'. So, in case you're trying to focus on what a particular endpoint is doing…
I don’t know if it exists already, but bazel would be very useful for the same type of MCP server. Since all dependencies are explicit you can pretty easily do a bazel (r)deps query to find related targets.
DeepSeek V4 – almost on the frontier
321–330 of 420 posts
Re: DeepSeek V4 – almost on the frontier
#322Earlier quoted context omitted.
Yes, my safety cap policy is definitely anti-social.
"These safety rails" was referring to LLMs, which have far more nuanced and capable safety rails than chemical caps do, and accordingly also have much more assertive ways to enforce them.
Re: DeepSeek V4 – almost on the frontier
#323Earlier quoted context omitted.
I don't think that "dystopian" necessarily goes far enough, this would be one of the rare times where I would call it a fascist mentality - the idea that everything's primary allegiance is to the state and the goals of the state rather than those of the customer or the user. I want a default that has people empowered, rather than something where it's just another performative smokescreen caused by overzealous product…
"the state" is just shorthand we use for "other people in my community" > I'll thank you and your kind for needing to distractedly tap the "Agree" button on my car's infotainment every time I start it to confirm that I will pay attention to the road. Does that actually mitigate antisocial usecases? No? Then it's not what I'm talking about :) Of course if you wanted to you could just share specifically what totally-re…
It's a very different abstraction layer, in the same way as individual cells vs the entity that is you. The entity that comes together from all those "other people in my community" and its priorities are different to the individual desires.
> Does that actually mitigate antisocial usecases? No? Then it's not what I'm talking about :)
Maybe it does? Maybe someone is alive on the road today because they read the message and changed their behaviour. I'm giving an example of something where this liability mindset has created a world where manufacturers are no longer prioritising the desires of their users in order to appease a sense of harm-reduction. And you weren't limiting it to LLMs you were applying it to all sorts of tools.
I think that "reverse engineering" as the OP was talking about is one of those things where maybe 1/10000 uses could actually be harmful. This is not even a high-risk request such as to produce a weapon of some kind where maybe your "antisocial usecases" could be applied.
Re: DeepSeek V4 – almost on the frontier
#324Earlier quoted context omitted.
The difference is IDA Pro doesn’t do something unless you instruct it to, an LLM is unpredictable and may end up performing an action you did not intend. I see it often, it presents me options and does wait for my response, just starts doing what it thinks I want.
This. It's going to be tricky for the frontier model labs to argue they didn't intentionally design their models to do so, when the models take illegal actions. I'm not even sure how one would construct a viable legal argument around that for SOTA models + harnesses, given the amount of creative choices that go into building them. It'd be something like "Yes, we spent billions of dollars and thousands of person-hours…
So if I ask “how does a real world production quality database implement indexes?” And it says “I disassembled Oracle and it does XYZ” then I am liable and owe Oracle a zillion dollars?
Whereas if I caveat “you may look at the PostgreSQL or SQLite or other free database engine source code, or industry studies, academic papers; you may not disassemble anything or touch any commercial software” - if it does, I’m still liable?
Who would dare use an LLM for anything in those circumstances?
Re: DeepSeek V4 – almost on the frontier
#325Earlier quoted context omitted.
> I'm not even sure how one would construct a viable legal argument around that for SOTA models + harnesses, given the amount of creative choices that go into building them. I'm not a lawyer, but to me the legal case seems pretty obvious. "We spent billions of dollars creating this thing to be a good programmer, but we did not intend for it to reverse engineer Oracle's database. No creative effort was spent making it…
> No creative effort was spent making it good at reverse engineering Oracle's database. That's the bit that's going to be nasty in evidence. 'So you didn't have any reverse engineering in your training or testing sets?'
Re: DeepSeek V4 – almost on the frontier
#326Earlier quoted context omitted.
We have an enterprise cursor account so I can try all the mainstream models. Using composer 2 on our own code which I obviously have the source code for I couldn't get it to turn on a debug flag to bypass license checks while I was troubleshooting something. Infuriating. It was like that old Patrick from SpongeBob meme. I don't understand why we would turn the models into law enforcement officers. Things that are ill…
> Things that are illegal are still illegal and we have professionals to deal with crimes. This is quite naive take though. The direction of travel is more fascism in Western governments where duties of traditional policing are taken over by big corporations whilst police forces are being gutted and made impotent.
Re: DeepSeek V4 – almost on the frontier
#327Earlier quoted context omitted.
We need that lawsuit to happen already so we can establish precedent. The person in the driver's seat of the Tesla should be at fault. The engineer using the llm should be at fault. The person behind the gun not the manufacturer should be at fault.
We shouldn't need a lawsuit. The legislative branch should pass a law clarifying those things, that's their job.
Re: DeepSeek V4 – almost on the frontier
#328Re: DeepSeek V4 – almost on the frontier
#329Earlier quoted context omitted.
> I'm not even sure how one would construct a viable legal argument around that for SOTA models + harnesses, given the amount of creative choices that go into building them. I'm not a lawyer, but to me the legal case seems pretty obvious. "We spent billions of dollars creating this thing to be a good programmer, but we did not intend for it to reverse engineer Oracle's database. No creative effort was spent making it…
> No creative effort was spent making it good at reverse engineering Oracle's database. That's the bit that's going to be nasty in evidence. 'So you didn't have any reverse engineering in your training or testing sets?'
Re: DeepSeek V4 – almost on the frontier
#330Earlier quoted context omitted.
> I don't understand why we would turn the models into law enforcement officers It's a simple corporate risk minimization strategy. Just look at how universally despised Grok is on HN. Not because it's a bad model, but because it has less aggressive alignment which means it can be coaxed into saying things that get Xai pilloried here and elsewhere.
No, they've clearly put a lot of work into alignment. It's just that they've been trying to align it with Elon Musk rather than Amanda Askell. Unfortunately the more anti-woke they try to make it, the worse it seems to perform.
Probably because being anti-woke generally goes hand in hand with going against facts and logic. Cull the "woke", lose the facts+logic. Not that they care about that anyway.