[dead]
DeepSeek V4 – almost on the frontier
381–390 of 420 posts
Re: DeepSeek V4 – almost on the frontier
#382Run it on an NVIDIA GPU and charge $20 a month, and it becomes 'frontier.' That is what the term means these days. In terms of performance, it beats ChatGPT 5.5 and Mythos on several metrics.
Re: DeepSeek V4 – almost on the frontier
#383perhaps the capital market do not want to see it because it does not want to ruin o&a's IPO?
Re: DeepSeek V4 – almost on the frontier
#384Does it censor mentions of what happened in Tiananmen Square in 1989?
Do we test American AIs regarding what they would say about George Floyd or whatever the current stigma in the US is? Just for, uh, objectivity?
Re: DeepSeek V4 – almost on the frontier
#385Earlier 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.
> The person in the driver's seat of the Tesla should be at fault. I don't think this is a good analogy. For Tesla right now it might fly. However, when their software gets to waymo level of autonomy, I would expect liability to shift to the manufacturer. If anything, I think that would be the true proof of a company trusting their software to allow for autonomous driving
Also especially if they claim they're selling autonomous cars
Re: DeepSeek V4 – almost on the frontier
#386Earlier quoted context omitted.
> I even got a warning on my OpenAI account. This idea of software threatening the user with consequences is totally wild and dystopian. Fellow developers, what kind of world have be built? This is insanity. Imagine if my hammer told me, "Hey, you shouldn't use me on screws--only nails. Do it again and I'll self-destruct!" WTF people, stop making this kind of software!
> This idea of software threatening the user with consequences is totally wild and dystopian. This idea of software built on top of reverse-engineered data threatening the user with consequences is what's really even wild and dystopian.
god you're so right
Re: DeepSeek V4 – almost on the frontier
#387I'm surprised that people here don't care at all about these models openly training on your data, especially if you use them straight from the model developer. Whereas things like "GitHub now automatically opts everyone into using their code for model training" get hundreds of justifiably angry comments, I never see this brought up anymore on posts like these talking about using Chinese models through OpenRouter. Thi…
thanks for the heads up on github
Re: DeepSeek V4 – almost on the frontier
#388Earlier 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…
to what does the "it" in "I couldn't get it to turn on a debug flag" refer to?
Composer
Re: DeepSeek V4 – almost on the frontier
#389I'm surprised that people here don't care at all about these models openly training on your data, especially if you use them straight from the model developer. Whereas things like "GitHub now automatically opts everyone into using their code for model training" get hundreds of justifiably angry comments, I never see this brought up anymore on posts like these talking about using Chinese models through OpenRouter. Thi…
Are you implying chinese models training on my data is worse than OpenAI/Grok/Claude training on my data?
Re: DeepSeek V4 – almost on the frontier
#390Earlier quoted context omitted.
You can use Tinfoil for inference, which lets you use the model in the cloud while getting similar privacy as running locally: https://tinfoil.sh/inference . Disclaimer I'm the cofounder. This works by running the model inside a secure enclave (using NVIDIA confidential computing) and verifying the open source code running inside the enclave matches the runtime attestation. The docs walk you through the verification…
Worth noting that NVIDIA confidential computing and similar schemes have been compromised and shouldn't be relied upon if it really matters. See https://tee.fail/ and similar.
I was interested in trusted execution environments and how safe they were. If you look on google scholar and start reading, they seem super vulnerable. The feeling is that the industry has no better option and that they are a way to tell customers they are safe when they're not