xdg already provides "portals" and "XDG Intents" that implement most of what android does. Flatpak implements most of the sandboxing you have on android. It doesn't have feature parity but IMO it doesn't need to. CGroups and systemd-user can prevent apps from running in the background.

Code names for phones, all android builds (including official ones) have them.

https://storage.googleapis.com/play_public/supported_devices...

For a slightly more manageable list, the 590 of those that are or were supported officially are also listed on the LineageOS wiki [1].

[1] https://wiki.lineageos.org/devices/

My device is not even listed there, so I suppose many others also run Lineage on plenty of unvendored devices.

It's not Broadcom so it is supportable by OpenWrt. It runs Qualcomm IPQ5332 SoC which recently got supported in upstream linux ath12k drivers... There are a few patches to make it work and the only blocking issue is with the Realtek switch connected to the LAN ports.

N95 was not "meager" for it's time - it was faster than the first iPhone.

Mainly because Microsoft wants to have "connected standby": the CPU is running in a low power mode (not powered off like "old" S3 sleep), can be turned on periodically and can turn on other devices even when the computer is "sleeping".

My Zen2 based Lenovo laptop has 6-7 hours of battery when doing basic tasks in both Windows and Linux, but sleep on Linux lasts a week while on Windows it's empty in 24 hours.

> Mainly because Microsoft wants to have "connected standby"...

And that is OK, as long as they provide a way for you to disable it. I do not want my laptop to be doing things when I put it in sleep mode. Nothing at all. Save battery life above all else when sleeping. But Microsoft does not appear to provide a way to do that. At least none that I can see.

Macs have that too, just implemented well. In addition, CPUs with connected standby don’t have the normal sleep so even on linux they run in connected standby. Maybe its less buggy in your case? Consider yourself lucky, lots of people encounter problems with sleep on linux

> lots of people encounter problems with sleep on linux

Yeah, because they buy a Windows laptop, slap Linux on it, and expect it to work.

OSX sucks even more by this metric; it won't even install!

I was looking into hibernation on my Framework 13 with Ubuntu. Debian doesn't support it with SecureBoot enabled. Now you might say "just disable SecureBoot", but that is a whole new concept to understand.

I've found suspend performance has improved since upgrading to a kernel that supports the AMD 7640U NPU cores. I have no concrete evidence of that though.

I'm happy to accept poorer sleep performance to have a repairable laptop and Linux OSS (with good support), but I wouldn't say its problem free.

Well if you buy a Linux laptop and slap Windows on it, sleep will most likely work. Unfortunately Microsoft got preferential treatment.

This post is everything wrong with the world today. Installing software should not be gate-kept.

Who's to say that some current or future government in the US wouldn't use the data to prosecute dissent guaranteed by the constitution?

And it can fail in great ways. Last example: I asked claude for a non-trivial backup and recovery script using restic. I gave it the whole restic repo and it still made up parameters that don't exist in the code (but exist in a pull request that's been sitting not merged for 10+ months).

Interesting. I don't think I've seen hallucinations at that level when it's referencing source code.

Though my workflow always starts in plan mode where Claude is clearly more thorough (which is the reason it takes 10x as long as going straight to impl). I rarely skip it.

I think this is a snap issue.

I’d imagine that all of Canonical’s flavors/spins ship with snap, so if the resources are lighter on say xubuntu then it’s probably not snap.

Snap still kinda egh though ;-D

And they are the only real solution. Demand fitting production is never going to work unless we give up all the autonomy.

It will be a mix. There is certainly still a lot which can be done on the demand side, e.g. when to cool a cool storage house during the day, or when to run certain production lines.

SNI routing is such a bad way to do what should be L3 problem that people implemented PROXY protocol to send information about user's endpoint address without doing MITM.