tedivm

I'm rally disappointed in the Apple response here. I can't understand why they wouldn't consider `/etc/ssl/cert.pem` in scope for a security update. This arbitrary boundary has no justification at all, and makes people less secure.

Come on Apple, do better.

That's what I expect as well, there's really no other reason to use a model that is so far out of date.

I think if you're going to claim that Chinese AI is making things less secure for people out of China you need to back that up with models that are actually in use. Is this a real problem today, or a problem with a specific model and it's training? It's pretty freaking relevant if you ask me.

Qwen3-Coder is from August 2025. That is ancient. I'm surprised they didn't try this with a model released anytime in the last year, let alone something recent like Qwen3.8.

There was a ton of criticism beyond "ai bad". A complete rewrite, in a different language, is a brand new project. It doesn't have any where near the hardening as the previous version thousands of deployments. If they had done that exact same thing but without AI people still would have been upset.

The benchmarks show it is on par or worse than even older LLM models.

* With jev-sec-bench the confidence numbers reached roughly the same as Qwen2.5-7b-instruct (confidence was off by about 6% on average in both cases).

* On the OpenRouter Banking 77 benchmark Jev did the worst out of all the models, being about 25 points off from reality.

I also think the fact that Jev hasn't published any real papers or actual technical details should make people a bit more skeptical than they have been.

I don't self host anymore, as it really is a pain, but use Fastmail instead (while my wife uses Protonmail). I would never rely on Google for, well, anything if I can help it.

I think an interesting side of this conversation is how the Google employees are jumping in with DARVO attacks, trying to accuse people of spreading misinformation when they're literally quoting the ToS.

This is something I've seen happen a lot with Google- their employees (especially the director+ folks) are absolutely rabid on social media when it comes to defending their products, and they don't let little things like "facts" get in the way.

Google needs to get a better social media policy because they look like clowns when they do this.

There are a ton of advantages to using uv over pip. I don't use UV because it's faster, although I do appreciate that. I use it because it's smart enough to manage virtual environments for each environment and tool, it can isolate to different python versions trivially, and it handles locking in a way that is actual sane.

Seriously, even as well paid as many devs are these are not machines that are affordable for personal use. Their market is people slapping down millions on frontier model training.

>Indeed, the broad backlash against Flock has grown so strong that the surveillance company last week announced mandatory new audit controls and lower default data retention periods for US users.

I'm a bit disappointed that they didn't call out how much bullshit was in that statement. They are just changing the default settings for new customers. That's it. All the deployed cameras remain the same, and new customers can just toggle those settings off of the defaults. It is so obvious that they were attempting to get credit for doing nothing, and reporters should call that out.