• 34 Posts
  • 380 Comments
Joined 3 years ago
cake
Cake day: November 27th, 2023

help-circle
  • For anonymity alone, no. You ought to at least aspire to live the nomad lifestyle first and put up with its challenges, then enjoy whatever anonymity comes from it as a bonus.

    If you don’t mind apartment living, you could consider the arrangement I had at one point. Private landlord who didn’t run background checks, accepted payment in any reasonable form, many tenants, communal mailbox without apartment numbers or names required. Internet, utilities, etc. all rolled into rent and not individually metered. Might be harder to find but they exist.


  • As others have said, no because Google’s components have very good backward compatibility and will come for your device on its stock OS.

    I had other vendors in mind when I first read your question. In a sense, older ones could spy less as a side effect of vendor telemetry servers going dark over the years. Samsung also wasn’t as rampant with their spying back then. But either way, such phones would have been long without any security updates.



  • As someone who has used X11 and Wayland, it doesn’t matter for the typical user. If you, like me, have a penchant for some smaller desktop environments like XFCE or window managers, you will be stuck with X11, but many are already working on porting to Wayland.

    Couple edge cases for gaming, namely screen tearing on some X11 configurations and certain Nvidia hardware running into issues on Wayland. For multi-monitor or high DPI users, Wayland handles per-monitor DPI and fractional scaling far better than X11. Maybe a couple more edge use cases for remoting into the desktop, but Wayland support is also improving quickly on that end. In any case, Wayland is by design more secure than X11.



  • Meanwhile, I’m fighting to get rid of the password on the keyring each time it comes back by itself. For context, my root partition is encrypted, so it’s not a huge deal if the keyring stored on it doesn’t have its own password, I think. I set up autologin to avoid a duplicate password, but since the session manager no longer unlocks the keyring, the keyring must have no password else I get a password prompt all over again. There’s probably a more elegant way, but I’ve yet to find it.



  • Nearly everything that both requires a phone and disrespects my privacy has been work-related, so using 2 phones has been a solid choice for me.

    The work phone has a sim from a mainstream carrier and only gets powered on while at work during work hours. Maybe I’m spoiled that my workplace tolerates this arrangement. I couldn’t imagine having to be reachable any time of the day. I didn’t intentionally buy a separate phone, it’s just my old phone repurposed.

    The personal phone has an “IoT” SIM which can be purchased non-KYC where I live. All FOSS apps and a personal number via VoIP.

    I know it isn’t by any means airtight, but it gives infinitely more peace of mind than just trusting whatever sandboxing mechanism available on one device will be sufficient.




  • As long as you have a strong backup strategy, I would recommend full disk encryption during installation, especially if for a laptop. Peace of mind with negligible cost on modern hardware. Even accessing the encrypted disk from a live USB takes only two extra commands compared to an unencrypted disk. As long as the LUKS header doesn’t corrupt, hence the need for good backups.