You don't have to melt through that adhesive - it's incredibly weak and you can just pop it out with a sufficiently thin pry bar. This guide [1] does it with an iSesamo, but I just used a utility knife since I had one on hand and wasn't particularly concerned with scratches (the entire seam is covered by the headphone pads, so scratches around it are invisible).
The only AF systems that use LIDAR are the one on the newest Hasselblad medium format mirrorless cameras (since DJI owns Hasselblad and can leverage the tech from drones/cinema cameras) and possibly some phones.
I suspect it's fairly challenging to implement since the LIDAR sensor doesn't operate through the lens, so you'd have to continuously align the depth map with the image to account for parallax; plus it's only useful for close-ish distances (since the lasers can't be too powerful) and can cause unwanted focus behavior with windows or reflections.
Replacing the batteries on the Maxes is actually a fairly straightforward process (no adhesive melting required, just a screwdriver and a pry bar), and spare batteries can be purchased on Amazon or Ebay for around 50 USD. It's one of the better Apple products in that regard, very unlike the in-ear models.
It's nice to see some high-performance linear algebra code done in a modern lanugage! Would love to see more!
Is your approach specific to the case where the matrix fits inside cache, but the memory footprint of the basis causes performance issues? Most of the communication-avoiding Krylov works I've seen, e.g [0,1] seem to assume that if the matrix fits, so will its basis, and so end up doing some partitioning row-wise for the 'large matrix' case; I'm curious what your application is.
It's possible to use Tailscale with just a passkey [0], but it's a weird process because they don't let you create a tailnet and a passkey account at the same time. Instead, you need to create an account with a throwaway FAANG credential and send yourself an invite to that account's tailnet, and then use that invite to create a passkey-linked Tailscale account. This account can then create its own tailnet, at which point the original tailnet (and the throwaway FAANG account) can be discarded.
It's a weird process and not particularly user friendly (passkey accounts are tied to a specific passkey and can't have additional ones added, so you need to create a new account if you, say, migrate from one hardware key to another). Hopefully they improve the process before passkey support goes out of beta.
Do you have a feel for how the maneuverability of a B-1 being controlled by the canards compares to that of a typical airliner?
It seems like a system like this would need to respond very quickly to changes in the air mass, and the weight and slow response of an airliner might make this system less feasible unless you could somehow measure airflow a reasonable distance in front of the plane.
Based on my recollection of a conversation with the authors after their STOC talk: the RAM scheme is not efficient enough to be competitive with circuit-based FHE schemes; for problems with low RAM usage, existing circuit-based methods are more efficient, and problems with higher RAM usage are infeasible to run on any FHE method right now.
They were 50/50 on whether or not this technique could be made feasible in the same way that, say, the CKKS scheme is.