Kuinox

I answered about tokens being apparently something not measurable, I do agree that there is a lack of transparency on the subscription usage.

> "your usage will be measured in tokens, which we do not define, nor give you a way to measure them

They have an open source tokenizer on GitHub, they indicate which tokenizer they use per model, and they have a simple to use website that tokenize text and visualize it.

I dont read the argument as specifically AI being bad at the physical world but more that they can't be creative, physical world or not

> It’s not dead. Some companies use it while I believe the majority of use cases are addressed by open-weight rivals.

The quality of the answers on my datasets are in another league compared to the benchmarks. I have a mixed language dataset, Jev answers only lack some accuracy, the open weight rivals output just look like random noise

This is the same thing as "but AI can only repeat what it already saw" but the goalpost moved again.

> Not in rural Europe it isn't. > There is still no widespread charging infra.

You can charge your car at home on a simple reinforced 230V socket. Even city car which should be bad for this purpose have at least 200km of range.

AI are excellent at ingesting tons of data and getting something relevant from what you asked. I ask it about linux behavior and it will dig through hundreds of patches & mails and will return me informations sourced with links to the patches, mails containing it's affirmations.

Codex found the root cause:

> The site’s graph incorrectly uses 32 texture bindings, exceeding its WebGPU device’s limit of 16. > Firefox 153 mishandles that failed rendering operation and leaves the compositor waiting

So a firefox + website bug

With an updated firefox, the website works except the mindmap on the top right

> Uncaptured WebGPU error: Too many bindings of type SampledTextures in Stage ShaderStages(FRAGMENT), limit is 16, count was 32. Check the limit `max_sampled_textures_per_shader_stage` passed to `Adapter::request_device`

Works on phone but not on my linux desktop.

I cant select text nor click links on this page with firefox.

There is more to the browser, it can give you a remote desktop access to the browser.

So it's not completely headless.

But when I tried it, the remote control completely froze after a few seconds.

It's incredibly slow for a single core, that's my reference point.

1.4 billions requests, 258 160 cpu hours. That's 1.5 requests per second ? I'm starting to believe, the issue is more that their software is not well optimized.

Claude did the changes, I didn't do anything, I think it's was mostly recompiling with flags.

I did a similar thing recently.

I run kube in a VM, and it was ressource constrained.

I hooked an old samsung to my pc and have let claude handle everything.

I only had to unlock the bootloader, flash the image claude uploaded.

It rebuilt postmarketos multiples times to enable various flag, and now there is a kube node running on it.