How would you implement it? On a glass that the user controls (root), it would be impossible. Of course, I do not like bathroom recordings, but there’s no sane way to block them.

What is OPAL, and does it allow one OS to run without device-specific porting?

My dream phone:

• UEFI (can boot any OS without 2 months of porting and a risk of bricking)
• Repairable, but also upgradeable (thanks to UEFI)
• Keyboard

Ooh, JSON! The Electron crowd can now extend to the FS!

Torvalds is not vibe coding, and he doesn’t control the OS (GNU/Linux) anyways.

Thankfully it looks so unserious that it will not capture anyone except ‘windows/mac power users’.

It preinstalls their app.

They have repos now, but nothing in them is too advanced, and they absolutely do not deserve the money. GNU/Linux Mint offers THREE great desktop experiences, which are not kitsch slop (even if you don’t like them, they’re very high-quality) and have a much smaller budget.

They are nonfree.

Probably because Omarchy is preinstalling 1password.

To me it isn’t pretty, just kitsch.

Oh, and I am on the Moto/Lenovo ThinkPhone, by the way.

Motorola ThinkPhone.

I am very pleased. It runs all the apps a desktop GNU/Linux runs. There are many apps from GNOME which have a small enough window, they aren’t very advanced, but the only way to get better apps is to actually use the phone with them (I am actually planning on writing some apps, whose GUI should fit this small screen too). However:

1. Waydroid exists, though it is much worse than on a PC for some reason. It cannot play sounds, it does not have a shared clipboard and it crashes the compositor when trying to play a video. I am primarily using it for WhatsApp (which also drains the battery a lot). But it’s Meta’s fault: if they allowed us, I would have been writing a custom client.
2. The camera app is pretty basic, I am probably going to write a new one including manual controls (tell me if you’re interested). Most normal GNU/Linux camera apps will not open the camera, because it is not bridged to libcamera apparently, though it will probably be bridged at some point.
3. You do not really feel that you have Android drivers, they are pretty well masked.
4. The proximity sensor is buggy (often, when the phone rang in a pocket, it would not allow lighting up the screen until the ring ended) and so I disabled it completely.
5. Battery life is actually OK (without Waydroid running), but I haven’t measured. What’s impressive is that the phone never suspends, and the battery is still OK. With WhatsApp in Waydroid, it is short.
6. As a phone, it is reliable, it does not drop calls.
7. Of course, it is not treacherous computing and so it doesn’t pass Play ‘Integrity’. If you’re in the EU, in 2028 banks will be required to provide non-smartphone access to services (see the new PSR), but we have to see if the new ‘age verification’ app will not do the opposite. I am not accepting it on Android/iOS, as it should be possible to have the same functionality by using a web portal with a smart card reader (see my GitHub thread about it).

Yes, there are disadvantages, but I am enjoying the vastly greater freedom and it’s the first time I can say that my phone isn’t working against me.

Thankfully, I switched to Droidian at the start of this year. I am NOT looking back.

That’s what I mean. The protocol should be open, so that the software (at least the one running on my host, the opaque smart card does not telecommunicate and is ROM) can be implemented by anyone. No, I would not accept a version that works on some immutable desktop OS with a nonfree client.

It won’t count, and I can’t isolate myself completely.

What IS going to convince them then? I am NOT using Android or iOS.

The thing is that while the EU standard does not limit hardware platforms, it does not mandate neutrality, so I can expect member states to only implement Android/iOS. In any case, I will not use that.

It needs ‘hardware attestation’, so a closed set of OS. It would be much better without any age verification.