On the other hand, 5 minutes is already a huge improvement over 15-30 minutes, and it’s fast enough to remove much of the friction of recharging an EV.

Really wish this kind of tech would come to North America…

The most plausible output might be correct, or it might be utter bullshit hallucinations that only sound correct; the only way to tell is to actually try it or cross-reference primary sources. Unless you do, the AI answer is worthless.

The reason why they're getting so good at code now is that they can check their output by running and testing it; if you're just prompting questions into a chatbot and then copying their output verbatim to a comment, you're not adding any meaningful value.

With JPEG one of the big problems is that the data is Huffman-encoded without any inter-block markers (except maybe Restart Markers, if you're lucky). This means that a single bitflip can result in a code changing length, causing frameshifts in many subsequent blocks and rendering them all undecodable. If you have a large block of missing data (e.g. a 4k-byte sector of zeros), then you have to guess where in the image the bitstream resumes, in addition to guessing the value of the running DC components.

While it feels unlikely that a simple "write this spec from this code" + "write this code from this spec" loop would actually trigger this kind of hiding behaviour, an LLM trained to accurately reproduce code from such a loop definitely would be capable of hiding code details within the spec - and you can't reasonably prove that the frontier LLMs have not been trained to do so.

Of course, Chinese characters are not pictographic and haven't been for a few thousand years, but they are still largely ideographic.

Unfortunately, it gets cut off here:

``` ## CRITICAL RULES 1. *No tool leakage* — never output ```

I would be very interested to know what string is being blocked here, and what the rest of its critical rules are. Maybe some hex-encoding or other obfuscation could be used to coax the rest of the system prompt out of the model? I wonder if the next tokens here are consumed by the middleware (to execute tools?).

My favorite trick, which I’ve used frequently (including in scientific publications on lag!) is to use the slo-mo cam on a smartphone. Phones will usually do anywhere from 120-240Hz. Set up the camera so it can see both your input (e.g. a side view of you pushing a button) and the display, record a video, and then pull it into a media player that supports frame-by-frame playback. You can then measure the number of frames elapsed from you pushing the button (pressing it down far enough to electrically activate it) and the corresponding reaction on screen. This gives you a cheap and easy setup capable of measuring latency down to ~4ms granularity, and doing a few repeated measurements can give you a very accurate picture of latency. Keep in mind that latency is a range (statistical distribution), not a single number, so you need repeated measurements to understand the shape of the distribution.

If you’re developing a game, you can add a prominent frame counter on screen to be captured on the video, and add the frame counter to your log output. Then you can match up the video with your game’s events, after accounting for display latency.

> It was impossible to work out who, or where, Lucy was.

Lucy is a pseudonym. They were trying to get Facebook to tell them who the girl was through facial recognition. There’s no reason to expect a priori that the offender would be in any registry.

All I could think was, "good luck" and I certainly hope their app never processes anything important...

I've also used a logic analyzer to debug communications protocols quite a few times in my career, and I've grown to rather like that sort of work, tedious as it may be.

Just this week I built a VFS using FUSE and managed to kernel panic my Mac a half-dozen times. Very fun debugging times.

Also - if these things produce ethanol, even small amounts, are they going to be safe for children? The assumption here is that this strain would be passed mother-to-child, so this isn’t an unreasonable concern.

The WH using social media (X, Pravda Social) for official communication is highly deliberate - they get to declare post-hoc what is actually real communication and what is “just memes”. Of course it won’t make any difference to people amplifying the content. If the WH had to stick to traditional outlets for news they wouldn’t have this fig leaf to hide behind.

I'm fairly sure I know what the problem is! It was restored from a backup taken on an iPhone X that had two physical SIM slots (Chinese version). The new phone now seems to think it has two physical SIM slots: it shows an IMEI2 in About, but any attempt to use the eSIM functionality just fails (scanning a code does "nothing"; no "add" button is visible, etc.).

If this was an Android phone, I'd root it and just fix the offending network configuration file. I believe it's possible to tamper with a backup of the phone to fix the issue, but this would mean a full backup+restore cycle and some specialized tooling to go mucking with the backup.

I filed a Radar on it ages ago, but I'm assuming nobody ever picked it up.