comex

Correct.

I'm skeptical that this particular task would get blocked, though I could be wrong. But I agree that the moat is a problem in the general case.

Presumably yes. It is safe to assume that algorithms running the model changed, the training procedures changed, and the scale changed. Unfortunately the AI companies refuse to disclose the details of any of this, which is a harm to human knowledge (hopefully a temporary one). Yet the results speak for themselves.

For me it's only been in the last month with Opus 5.5 that I've been seeing code quality I actually respect (though this is with substantial human effort in the loop). Though this experience is from work where I don't have access to non-Anthropic models, nor Fable.

I agree, with respect to the status quo where AI writing is associated with lower quality.

In the long term, AI writing - mostly done solo, not directed by humans - will likely have higher quality than human writing, while being better suited to people's tastes since it can be personalized for every reader. If so, it's not hard to imagine it crowding out human writing.

You might ask, though, is that a bad thing? If it's legitimately higher quality, then what's wrong with consuming it? Well, I don't know. It certainly seems dangerous for everyone to be in their own little bubble of content. Social media of course tries to do that today, but there are limits. You can't pick any topic, any set of attitudes you want and get an infinite supply of content tailored exactly for you. Even if you find some super niche community to set up shop in, it's still a community; you're still exposed to the outside world at least a little. What happens when that changes?

It can’t, because passkeys are bound to specific domains and you simply aren’t given the option to log in with a passkey on the wrong domain.

At least on iOS it’s any app that implements the protocol. That includes Bitwarden, which is server-based but self-hostable. In the future it should also include apps like Strongbox and KeePassium which store the private keys directly in a portable .kdbx file.

I’ve run into this issue multiple times, no custom hardware involved. Just virtual machines that didn’t support Bluetooth, and physically distant computers I was controlling remotely.

You don’t have to use a password manager that relies on an account. Personally I use Strongbox on iOS and macOS, which stores everything (including passkeys) in a .kdbx file. I then sync the .kdbx file over iCloud, but if I lost access to iCloud then there would still be copies of the file on all my devices. Overall this is not as secure as the more centralized alternatives, but it does leave me in control.

Though obnoxiously, the public computer login method doesn’t rely solely on the QR code it shows, but also uses Bluetooth. So if you want to log in on a VM or computer without Bluetooth, or a physically distant computer being accessed remotely, you have no choice but to install your password manager on that computer. Which is a lot less secure than copying a single password and one-time code.

The OpenWrt One is really not a great piece of hardware. No 6GHz, and only two Ethernet ports, one of which is only 1Gbit. The latest GL.iNet products are apparently better, but also apparently don't run stock OpenWrt, only a fork of it. In other words, there's still plenty of room in the market for good routers with open-source firmware.

I know how to flash firmware, but I'd still rather buy routers that have open-source firmware pre-flashed and tested by the vendor. This is simply because I've often run into issues with OpenWrt. I once bought a bunch of Archer C7s because it was described as a good router for OpenWrt, only to discover dmesg full of crashes from the proprietary wireless firmware running on the 5Ghz chip. In another case, I learned long after installing OpenWrt that the performance was much worse than stock firmware because OpenWrt didn't support hardware routing offload.

It's vibecoded - new, large codebases are par for the course.

(This used to come at the cost of code quality, but increasingly does not.)

It's unclear how big a role distillation plays, but it may be a big one. There's also a law of diminishing returns. To get a meaningful increase in model quality you seemingly need an exponentially larger model. And most people don't think K3 is actually on par with top closed models.

Many of those utilities, if you inspect the source code, are recognizably the same programs as their original versions written 30+ years ago. They’ve been maintained and changed over the years, sure, but they’ve rarely needed big changes. After all, they’re simple programs that do basically the same job today as they did then, using basically the same API surface.

The main issue with this is that the programs are usually still single-threaded. For some key utilities like find and grep, this has allowed more modern alternatives to leapfrog them in performance. (To be fair, it’s hard to add parallelism without breaking compatibility somewhat.)

But in most other respects, there’s nothing wrong with being a little old-fashioned. Using global variables is an example of that. It’s a problem in larger programs but at this scale it’s fine.

That doesn't really make a difference, as TCC permissions don't care if you're root or not.