xz-tools was only caught because it had a bug causing slow startups and someone was micro-benchmarking Postgres and decided to dive in further.
16,080 karma · joined August 29, 2017
Unless stated otherwise, opinions here are my own and personal.
xz-tools was only caught because it had a bug causing slow startups and someone was micro-benchmarking Postgres and decided to dive in further.
One of the certificates literally has a private key of 4; it's as compromised as it could quite possibly be. This is not a "one of the intermediates have a weak and possibly crackable key" or "a bunch of incorrect certs were issued but the issuance was patched".
To a MITM attacker, git clones can be easily distinguished from visiting in Safari. You could choose to only poison git clones; without poisoning anything else.
Heck, you can probably build an exploit kit in a hour; camp out around a Starbucks or McDonalds with open wifi, and start compromising git clones and deliver malicious payloads.
I can see (and believe) Astra beating GLM 5.3 on verifiable hard domains like maths, etc; but we’re at this stage where intelligence scores and even ‘frontier real world unsaturated benchmarks’ really doesn’t reflect real world use anymore.
One was rushed and same-day updated as GLM 5.3 (iirc) got added; of course its main change to rankings was lower GLM scores.
Yes, high-capacity LPDDR5X are made and do exist, but for all practical intents and purposes, you can't buy enough of them to deliver to customers at Apple scale.
It's just handy when you have a USB-A device and don't want a dongle, traveling, etc.
Benchmarks don’t really tell you much. For API best will always be a model+effort sweep on your internal evals (and if you don’t have internal evals, do that first).
For individual coding harnesses, honestly I just go with vibes. The best workflow is the one that works for you.
I wish Apple would make a similar device. I'm fine with recycled chips and getting a bit gimped on RAM size.
Like the MacBook Neo of iPads; I just really want a media consumption device. A20 Pro means nothing to me.
It also doesn't help that a lot of scammers use this, or fake cyber incidents, for phishing; so it's not like they have an easy solution for exempting "security emails" either.
Maybe it’s 1% or 10% today, but a decade ago, having/assembling the technical chops to know how to build something was a huge part of the meat / barrier to entry.
US commercial interest =/= OpenAI and Anthropic.
^Not recommended literally due to brownouts/etc, but a cheap power management IC on a breadboard can solve that. Alternatively, add a battery/etc.
Home solar panels and batteries are just like this except on a bigger scale; and with (hopefully) more QC.
Ask your agent to make you a visualisation, heat map, whatever. I bet it's just that you're using these models more, and for more complex tasks.
Compute, data, and parameter count are the three logarithmic values that correspond to model performance.
So if you find ways of improving training efficiency (the simplest conceptually is probably local/global sliding window attention like Gemma; the latest DeepSeek and Kimis have quite fancy ones), you will be able to have more effective compute, and train smarter models while keeping data and param count the same.
If you find this fascinating and want to dive more, I encourage checking out nanochat (solid GPT-2 repro; minimal LoC); and trying to make architectural tweaks with a coding agent.
“Learning through experimentation” has never been easier or more fun in my opinion. If you have a GPU, even an older 8GB card (or a few bucks for Runpod), you can pretrain your own small language model and start experimenting / tweaking it.
Still get the model out there.
These defenders aren’t supposed to have access to the “defender models”.
> Moreover, because iOS apps are sandboxed, as implemented in other jurisdictions, apps available through alternative distribution will be sandboxed, which further strengthens security and reduces the likelihood that any app will compromise other apps [...]
First, Apple does not follow the same rules they set for developers.
Second, Apple does not treat all developers equally. We have functionality we’re unable to offer to iOS users.
The same feature, including technical implementation mechanism, is available in Claude and Gemini. It’s unfair.
I like how the court’s declarations are punchy, factual, and dare I say obvious. I’d suggest giving section 1 a read.
There’s going to be a million “what ifs”, from walled gardens to security to ‘you don’t have to use iOS’, but it’s blatantly obvious this is all about competition and money.
It’s anticompetitive, illegal, and the remedy is to cease these anticompetitive actions.
Was there even an incident co-ordinator here? Was any of the parties talking to each other?