• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle



  • Immutable Nixos. My entire server deployment from partitioning to config is stored in git on all my machines.

    Every time I boot all runtime changes are “wiped”, which is really just BTRFS subvolume swapping.

    Persistence is possible, but I’m forced to deal with it otherwise it will get wiped on boot.

    I use LVM for mirrored volumes for local redundancy.

    My persisted volumes are backed up automatically to B2 Backblaze using rclone. I don’t backup everything. Stuff I can download again are skipped for example. I don’t have anything currently that requires putting a process in “maint mode” like a database getting corrupt if I backup while its being written to. When I did, I’d either script gracefully shutting down the process or use any export functionality if the process supported it.





  • As another poster said, the underlying tech is not private: https://jmp.chat/privacy

    For backwards compatibility, what your proposing is unlikely unless driven through regulation (personal opinion).

    Use something over the top (like Signal was suggested), use a non-KYC provider (like Jmp), or use a burner phone.

    A non-KYC provider I wouldn’t trust to be private personally, especially as a secondary SIM. Maybe slightly above average (the company can’t sell the number attached to my name), but I’m sure enough information leaks that a state-level actor could correlate the device to me. The IMEI the tower gets is probably enough to run to Google to figure out who bought the phone.

    Even burners may trace back to you through GPS or triangulation depending on how private you really want to be.