You don’t necessarily need QubesOS to get better isolation. You can package unsupported applications as Flatpaks yourself and run them with minimal permissions. The downside is the maintenance burden, and Flatpak sandboxing isn’t as strong as Qubes’ VM-based isolation. It’s a useful middle ground, but it doesn’t completely solve supply-chain risk. Qubes can be good, but it’s all about your friction budget.

Humans optimise for convenience eventually.

Phishing actually is a core branch of hacking—specifically under Social Engineering. It’s not really like walking through an unlocked door; it’s more like a con artist dressing up as a locksmith and convincing the homeowner to hand over the keys.

Hacking applies to the entire attack surface, which includes the human element, further more there are whole phishing campaigns that are heavily automated and often deliver stealer malware, making them a full cyber attack.

This wasn’t a technical compromise of Signal itself, but phishing/social engineering is still a form of hacking.

I’m pretty sure ⁠-r⁠ flag actually stands for ⁠–resizefs⁠. When you include it, ⁠lvextend⁠ automatically runs the appropriate resize command (⁠resize2fs⁠) for you in the background immediately after the volume is expanded.

Which makes it a convenient, single-step process.

Do a backup image of the partition first before you run these commands.

If you decide to use all free space: sudo lvextend -r -l +100%FREE /dev/ubuntu-vg/ubuntu-lv

Should suffice I’m pretty sure.

I think the setup script that applies the config changes is documented here: https://codeberg.org/celenity/Phoenix/src/branch/dev/docs/install.md

Something I’ve been thinking about: independent security projects often face pressure once corporate partnerships or funding enter the picture.

Does GrapheneOS have any structural safeguards to ensure development priorities remain community-driven if hardware vendors become more involved?

I’m not assuming there’s a problem — just interested in how projects like this avoid the “venture capital influence” problem that has affected other open source initiatives.