Native package manager > Native binaries > AppImage > Flatpak.

Yes, snap isn’t even on the scale.

They’re planning on making a version where everything is a snap. Performance and usability may come later, who knows.

“Stalled I/O” has entered the process list :D

Someone made that, sort of. Unfortunately, the privacy nightmare is slightly reduced compared to the original one.

https://github.com/openrecall/openrecall

The good old lying approach, I see.

I use a mouse btw.

For a lot of project “compiling yourself”, while obviously more involved than running some magic install command, is really not that tedious. Good projects have decent documentation in that regard and usually streamline everything down to a few things to configure and be done with it.

What’s aggravating is projects that explicitly go out of their way to make building them difficult, removing existing documentation and helper tools and replacing them with “use whatever we decided to use”. I hate these.

Fair. Also, flatpak does not try to break everything by default, which is a plus.

I like the “encryption, but we have the keys” approach. Makes it very secure, especially since MS never had any security breach or leak, ever.

HTTPS isn’t only about encryption; it’s about talking to the right servers.

Because they want to “protect” you from “yourself”. Imagine, you could scrape your own data that you can already see.

I’d be really worried if the security of server operation for my bank depended on the client-side. But playing devils advocate, some people will most likely point out that a root exploit on a phone may be unintentional and used to spy on people, to which I answer:

• show me a big scary box where I can “accept the risk” and move on
• keep in mind that if I am root on my phone, I can hide the fact that I am root on my phone and you’ll be none the wiser

Currently, option 2 is in effect, sadly.