I remember updating (maybe a year ago now) and it making all my containers unaccessable.

Victims of trauma dont just forget because time passes. They graduate (or dont) and move on in their lives, but the lingering effects of that traumatic experience shape the way the look at the worlds, whether they can trust, body disphoria, whether they can form long-lasting relationships, and other long last trauma responses. Time does not heal the wounds of trauma, they remain as scars that stay vulnerable forever (unless deliberate action is taken by the victim to dismantle the cognitive structure formed by the trauma event).

Librewolf for Desktop (fork of Firefox with Arkenfox user.js and removed Firefox anti-features) and Mull for Android (fork of Firefox which is deblobbed of proprietary blobs and uses much of Arkenfox’s user.js and Tor upstreamed privacy patches). Firefox’s Resist Fingerprint (RFP) is extremely important in my opinion for privacy because it normalizes much of the identifiers for better privacy. IceRaven still has proprietary blobs included for Google Safebrowsing and other things.

Mobile browser comparison: https://divestos.org/pages/browsers

If they want proper anonymity, the user needs to protect against fingerprinting from the duckduckgo website (Tor or Mullvad). If by anonymity you are meaning from OpenAI, then duckduckgo needs to be running user’s text prompts through a paraphrasing LLM to normalize text and avoid deanonimization using writing-style Fingerprinting.

Unofficial MCPE launcher is the only way to run bedrock on Linux

How recently. I tested with Mullvad and it gave me a notice.

They block VPN users.

deleted by creator

Microsoft Activation Scripts (MAS)

Alternatively to upgrading edition check out these apps:

• KDE Connect
• Syncthing

I very much recommend Kicksecure hardened Debian as a daily driver. Eventually I will test gaming on Kicksecure making use of the steam flatpak, but I currently dont have the time.

IIRC, there is a way to force hardened_malloc for flatpaks, but this breaks many flatpak applications. For another hardened by default OS distromorph (the process of turning one distro into another closely related derivative OS) check out secureblue

Requiring webassembly will break the website for most privacy hardened browsers (arkenfox, Librewolf, cromite, Mullvad, etc). Webassembly is disabled for security and privacy reasons in these browsers. Not worth IMO. See a short snippet of Arkenfox’s reasoning here: https://arkenfox.github.io/gui/?s=javascript.options.wasm

Ok, understandable. I hate mobile devices because of their limited usable life and limited OS compatiblity. Verified boot is nice, libre-android is better. Not worth it for a person of interest to install /e/OS, but neither would stock Android or AOSP without significant hardening. DivestOS is my top pick for degoogled Android, but as I learn more (been reading kicksecure’s wiki on mobile device security) maybe Root isn’t as bad as I thought for security. I trust Kicksecure’s security research because of their significance as the base OS for Whonix and Whonix-qubes.

Related to relockable bootloaders and the security they provide, I was under the impression that if a malicious bit of software were to make use of some privilege escalating vulnerability and modify the kernel, the phone would fail to run in some way (ignore the rest of this if that isn’t the case). I dont think security should be dependent on the user behavior in basically any case.

For example, a FOSS developer in our communities could suddenly lose it and modify an existing app of theirs to inject malicious code making use of a vulnerability in android and we’d have know what of knowing until the damage is reported. Good user behavior is very important for security, but we can’t all be auditing our apps for each new release, even though its quite unlikely to happen.

It still has much of the google proprietary blobs still included and relies on google services, also without significant effort to harden Android. I have also heard that sometimes they fall behind on updates to their apps by weeks at a time (correct me if I’m wrong I am still looking for the source I found this info from). It may be moderately degoogled, but their security just ain’t there. In some cases (like OEM EOSL for older devices) having a 3rd party ROM may improve security with more up to date patches. Unless the bootloader is relockable and secure boot is possible, you will be compromising your device’s security (and privacy along with it) and destroying the Android security model in general.

I’m out here living my comfy carpenter bee life eating wood and other shit

There is no android ROM that is fully degoogled without losing out on much of base Android’s functionality. See the table I link under the other person’s comment. I have also heard that /e/ OS falls behind on package updates from its forks of other projects, many of its default apps.

https://eylenburg.github.io/android_comparison.htm

/e/ is not very degoogled. DivestOS or GrapheneOS would be better choices, then maybe CalyxOS.

And install it as a PWA (it might just be a shortcut idk) on Android

Instead of Manjaro, if the goal is to use an Arch Linux based distros, EndeavourOS is a good option. It us popular, more user friendly then arch, sticks pretty close to Arch main, the community seems friendly, and offers ways to customize your software install on first-boot