> Building on theoretical work by Dietzfelbinger and Walzer [8], we propose a novel practical approach, the binary fuse filters. They are conceptually similar to xor filters, and they rely on nearly the same simple code.
For those that don't know why, and I didn't, the reason for this is that Tilapia are "mouth brooders", that is they keep the fertilised eggs in their mouth. So throwing away a dead female can cause these eggs to hatch, and reinfect the waters with new Tilapia.
An interesting article, however my question is technical.
In the "The Mechanism of Extraction" section, how is that image made? It is nicely laid out, and has a nice "hand-drawn" feel. This is a good format for many technical drawings, but I have not found any tools that could create this.
I stated using devcontainers through VSCode and find them incredibly helpful. It’s great for me to be able to load up exact coding environments on different computers. But, I only used them through VSCode.
When I wanted to branch out a bit (and especially using coding agents), I started using the CLI version more. I find devcontainers a great way to work with different coding projects and wanted to make sure people knew that there was a way to use them outside of VSCode.
The real question is how do you enforce that the human is reviewing and double-checking?
When the AI gets "good enough", and the review becomes largely rubber stamping, and 50% is pretty close to that, then you run the risk that a good percentage of the reviews are approved without real checks.
This is why nuclear operators and security scanning operators have regular "awareness checks". Is something like this also being done, and if so what is the failure rate of these checks?
In my experience, Gemini is great for "one-shot" work, and is my goto for "web" AI usage. Claude Code beats gemini-cli though. Gemini-cli isn't bad, but it's also not good.
I would love to try antigravity out some more, but last I don't think it is out of playground stage yet, and can't be used for anything remotely serious AFAIK.
Is there a fuller list of headsets that are affected being maintained anywhere? I could not find it. Since most manufacturers tend to reuse components, we can expect that more Sony stuff is affected, and probably more JBL/Jabra/Bose/Marshall that they didn't have access to.
Based on their timeline, full credit to Beyerdynamic!
Partial credit to Airoha, they took a long time to initiate the communications, but once they did, they seemed to take it seriously.
No credit to Sony and Marshall, as they either didn't, or effectively didn't, respond.
Unknown credit to Bose, JBL, Jabril, EarisMax, MoerLabs, and Teufel, as they don't appear in the timeline.
Honestly, even though it failed, I'm kind of impressed that the trajectory mostly stays in the lines. If you remove all but two openings, does it work? The drawing you show has more than two openings, some of which are inaccessible from the inside of the maze.
It's ASCII art, so the "trajectory" will always stay within the lines, because you can't have the ● and ║ characters intersect each other.
The only impressive part would be that the trajectory is "continuous", meaning for every ● there is always another ● character in one of the 4 adjacent positions.
> Building on theoretical work by Dietzfelbinger and Walzer [8], we propose a novel practical approach, the binary fuse filters. They are conceptually similar to xor filters, and they rely on nearly the same simple code.
reply