You seem to be falling for what the author was writing about. Only because you could technically try to use keepassxc to store passkeys, that does not mean that it will work. You see passkeys were build in a way the service you’re trying to login to can decide if they accept your keepassxc for passkey storage or not. It looks like you are in control when you are actually not.

There is no good reason so send the passwors itself to the server. Send the hash and you will have a fixes length of data to send anyway.

And even if insist in sending the password over the wire, there is no problem on the backend to handle longer passwords than that, so that no one will run into a limit in practice. We’re talking about bytes here, not even a kb.

Correct, I use Kast on the desktop, works nicely

If you’ve got a nextcloud somewhere, you already have everything you need running. Install required extension and login in antenna pod. Works nicely, can recommend it.

Good point. The author argues that:

they buy the device on your behalf so your real name never gets attached to it.

However it is relatively easy to attribute a sim card to person simply based on its usage. You also leave the same movement patterns on the mobile network. I don’t see a benefit here compared to just using a sim card from a service provider that does not sell their customer data.

Bummer… no mention of the drawbacks whatsoever.

Hopefully the court was clever enought to specify that the side loading must not be more difficult than installing via the store. Apple will for sure make it as complicated and user hostile as possible so they fulfill the ruling without having any practical impact.

Finally some good news