I'd recommend reading the post, it's not that long

As someone who doesn't know jj and read this article, it does sound like `git rebase -i` to me. I'm sure that if I actually spent time learning jj I'd know the difference though.

Is it possible to reason or prove the correctness of an LLM?

Not gp but I really like the sound of my GK Kuntens and 7Hz Zero2s. Both have a rather V-shaped sound signature, some like it and some don't. Though unfortunately the Zero2s feel a bit uncomfortable in my ears when using them for longer

I'd guess the speed improvement in those cases likely came from learning a better technique, like touch typing and using more of your fingers. Afaik a lot, if not most, of the fastest typists are still on qwerty.

I definitely learned to touch type with Dvorak, because I couldn't look at the keyboard anymore to get help.

That "officially supported" comes with a huge asterisk though. Security bulletins for old android versions already only include backports of high severity patches. On top of that the device also gets no security patches for firmware or kernel, as the hardware and kernel are eol. The FP5 is also on an eol kernel after less than 3 years, not that they were providing kernel updates in the first place. https://discuss.grapheneos.org/d/24134-devices-lacking-stand...

I thought it worked just fine on LTSC 2021 (21H2)

I think it could be interesting to explore Universal Blue based distros such as Bazzite for this kind of use cases. The OS comes from a standard OCI container image, which means you can create your own customized one by layering changes on top of an upstream base image.

I feel bad for the unsolicited distro plug though especially since you already have a solution that works well and you are familiar with, but I thought it might still be useful to mention it. I'm not sure if uBlue would even be better vs your current setup. Seems like netboot would still be needed to get the latest version without an extra reboot.

It seems this vuln was already publicized in june, or is that interview from earlier?

> For a lot stuff on my local network I don’t want the hassle and there are loads of use cases in local networks for normal people to just have port 80 no certs on something like 192.x.x.x because there is no easy way to set up public certificates for that and I don’t want everything hostem on cloud - some stuff I want to still host for myself in my local network.

Tbh I don't see what's hard about this. All you need is an A record pointing to your 192.x.x.x, acme capable dns host and a modern reverse proxy. You can even use a free ddns service if you want. Wouldn't bother with this for development, but anything hosted for longer than a few days absolutely yes. Imo not getting browser warnings is alone worth the few minutes it takes nowadays.

“ All you need is an A record pointing to your 192.x.x.x, acme capable dns host and a modern reverse proxy”. That’s a LOT more than socket(), listen(), and accept().

> All you need is an A record pointing to your 192.x.x.x, acme capable dns host and a modern reverse proxy

And to distribute keys that allow those appliances to update the DNS records, to secure those keys, have an a way to install those keys (and update/rotate them), and make sure your DNS host is supported by your acme client.

XD

I can yeah it is easy but I have 20 years of experience.

I don’t want to spend time setting that up.

For less technically capable people you just lost them in first sentence.

> But also, rewriting history only works if you haven't pushed code and are working as a solo developer.

Weird, works fine in our team. Force with lease allows me to push again and the most common type of branch is per-dev and short lived.