Probably extreme compression, their 4K streams are very low bandwidth.

That's an interesting statement coming from the guy who made Telegram that has no e2e encryption at all by default, so is guaranteed insecure.

Yes lots of them use cheap LEDs with poor CRI, high color temperature, and a huge blue spike in the spectrum. All of that leads to a very bright looking light that also doesn't let you see detail very well.

Bulbs that test well on spectrum and flicker tests, Phillips Ultra Definition is a good one I believe.

https://www.thesmarthomehookup.com/25-soft-white-led-light-b...

Nothing on the box really means anything, so many bulbs claim high CRI and everything but in reality have terrible spectrum. So you can only go off of actual real life testing from a third party.

Cost.

It's only 1 email account but with either catch-all or aliases configured.

Each site should ideally have a unique password so you only need to change that one.

Exactly! Then you write each password down in your notebook of passwords and pat yourself on the back for how hard it would be to compromise all your accounts in one go ;)

Even with graphene I don't believe it mitigates much as far as apps collecting data. The idea for more privacy is you run open source apps instead that just don't collect data.

AFAIK Graphene is oriented towards strong device security with privacy as more of a side effect.

One thing with the sandboxed Play Services being that Google has fewer permissions on the device, so presumably they can collect less data.

Which I believe is GrapheneOS' argument when people praise microG: microG being open source does not fundamentally add privacy: apps using microG will phone to Google's servers (that's the whole point of microG). What microG solves is that it removes the Play Services that are root on your device, and it turns out that sandboxed Play Services do that as well.

> The idea for more privacy is you run open source apps instead that just don't collect data.

Yep exactly, I just wanted to add about the sandboxed Play Services, because it was not obvious to me at first :)

Sure that's valid, they do need to conply with legal orders. But they don't need to store bitlocker keys in the first place, they only need to turn over data they actually have.

The average Linux VM I run is around 50-100MB of RAM usage. Not actually that much more than an LXC container.

There are some use cases for a VM over a container, sometimes you want better isolation (my public facing webserver runs in one), or a different OS for some reason (I run an OSX VM because its the only way to test a site in Safari).

Ok that is a very low usage. Alpine or so?

But yeah I just restrict my webserver in an unprivileged container. Though my site is static and accepts no input whatsoever.

Just a basic Debian install.

Containers also have some advantages for device passthrough, I have my Intel iGPU added into one for Immich and Frigate, can't do that with a VM unless you detach the whole GPU from the system.