croemer

Domain registration doesn't mean that much. Many similar domains are already registered, eg python2shell.com is 5k aftermarket but js2shell.com is unregistered. Might not be a bad investment to register the .com for all the top PLs.

I'm not sure I've ever read a sentence like this before LLMs. Maybe I didn't pay attention, possible. I should do a search of pre-LLM writing for this construction.

I see, you're updating the graph with 3 weeks delay, that's a bit confusing. Now there are 4 days at least.

That code font is painful to read, no syntax highlighting and extremely pixelated. It's retro but an eyesore.

This one sentence sounds very LLMish:

> Object storage as the source of truth gave the economics, and tiered NVMe SSD/memory caches gave the performance.

Thanks for the tip! Set it up locally and it works!

Is there a Jev-like model I can run on my Mac? Something like Ollama? Or what's the best way to play with it? Is there a cheap/free API service eg on OpenRouter?

Oh cool, I missed that the raw data is available. I shall see if I can do the analysis myself then.

This seems like a poorly executed analysis of very interesting underlying data.

With this degree of average age variability they can't compare failure rates.

They should show us Kaplan-Meier (survival) curves not failure in this quarter.

Unless they set some datacenter on fire, not much in Q2 should be different vs Q1 for the same hard drive other than it being older.

Sure, internally, I'd do a better analysis controlled for age that shows if there are common failure rate increases but here they focus on model failure rates which is completely confounded by age differences.

For those outside US, in Europe I got "Service unavailable".

Switched on US VPN and it works.

Edit: Now it seems to work. Maybe it was a glitch. Or a US government agent is watching this page.

The title is misleading, they found 24 vulnerabilities in Android _apps_ not in Android itself. That's a big difference.

In their own words from the body:

> I’ve reported more than 20 vulnerabilities in Android applications

Pretty crazy that the model doesn't know that it needs to stop before it hits 128k output tokens. I guess it has no sense of how many tokens in it is? Wouldn't this be possible to work into the architecture?

This is evidence that Sonnet 5.5 wasn't yet trained on the HN comments from the Opus 5.5 release. Maybe Pelicanmaxing will lead to 127000 thinking tokens being used on Max.