424 karma · joined April 10, 2015
turned out to be a bug in a patch, causing kv cache indices to be stored in too narrow variable types, making them wrap around.
fascinating, and slightly horrifying, that LLMs are able to notice that their output isn't what they meant to output. reminds me of the mirror test.
and skills from building with hand tools help you judge the results, but not necessarily with actually using the tools.
It's the same as age limits on energy drinks, alcohol, tobacco etc. More of an inconvenience than a restriction if someone is determined enough.
We should focus on having parents teach their kids what they should and shouldn't be doing, instead of "blocking" them and pretending that solves the issue.
Source? Can't find any good source on this.
Then you can be writing the code, with the LLM doing the "boring" parts, in chunks small enough you can review them on the fly.
Alternatively you could find some other people to share the HW cost and run some larger models (like Kimi-K2.5 at 1.1T params).
Examples:
- Each window is sealed under a thin polymer layer, balancing optical clarity with biocompatibility while preserving the ring’s continuous, scratch-resistant exterior. <- they're on the interior of the ring, and I'm assuming if they're polymer, they're not very scratch resistant.
- This flexible board architecture allows the Oura Ring to maintain its circular form as well as distribute heat [...] <- what heat? And how?
- The charging coil runs along the ring’s outer circumference [...] <- scan shows a small coil on the inside, not running along the circumference
- [...] we can easily visualize the deployment channel and insertion mechanism that guide this filament to its precise depth and angle. <- I can't see the insertion mechanism.
- spiral geometry <- the Bluetooth antenna isn't spiral. Nor does it communicate "through the user's skin"?
- miniature microphones (visible as small cylindrical cavities) <- they're rectangular.
Other times you just want to skim through the content, for example if you're already familiar with the topic, although you could argue that it's not really worth spending time on skimming something you're already familiar with.
But I definitely agree with the "quality filter" part. There's so much content out there that just doesn't have much substance to it.
Isn't that just because that's what they're being trained on though?
Wonder what you would get if the training data, instead of being task based, would consist of "wanting" to do something "on someone's own initiative".
Of course then one could argue it's just following a task of "doing things on its own initiative"...
They have a video with some more info here: https://pt.fourthievesvinegar.org/w/9aa66b49-2ec5-497f-9f49-...
And apparently the use of NSF does have a bunch of research papers written about it: https://www.researchgate.net/profile/Amol-Patil-43/publicati...
Does it really? In my opinion, if it stops working and it's under warranty, why not send it out for repair? They did no changes to the actual device, and apparently it was working fine for a few days without network connection, so if it suddenly stops working and it's under warranty that's the manufacturer's/store's problem, not theirs. Trying to fix it/reverse engineer it takes time, and I can see someone with these kinds of skills wanting to spend it on something else than trying to figure out how the manufacturer bricked their vacuum.
In addition, _someone_ is paying for the repairs under warranty, so if enough people were to do it, hopefully it would disincentivize completely blocking devices just because they can't reach a server.
At least they have a lifetime purchase option, though it costs $830!