I don't think cellular location would be excluded from such tracking tbh. I would rather not take my phone with me at all when visiting such a potentially sensitive place, or at the very least use a Faraday cage.
EngineerGaming
"Rabbit hole"? Isn't it as easy as just not going to a carrier's store for it?
We always bought from generic tech stores, almost always big chain ones - never got a carrier-locked device. Is it different in the US?
At least until the official client allows registration from desktop without VM shenanigans, and allows an arbitrary SOCKS proxy instead of just their own, and doesn't depend on Google services on mobile, there NEED to be third-party clients like signal-cli or Molly.
I don't think they're a honeypot, but they do seem like posers. Privacy is just good for marketing now.
That is exactly what I said though - passkeys are software. They're not confined to hardware modules, so there's no such thing as "device being a passkey".
From what I understand, "passkey" refers to software, so no such thing as "device being a passkey". Unlike a hardware key.
In case the device gets lost/stolen, you should have a backup of the database that contained the passkeys. That's why I would be only using the implementations that allow doing that easily.
What are you talking about? KeepassXC, to my knowledge, is not dependent on any TPM, snd it does support passkeys.
No, but this is very unlikely because I do keep regular backups manually. I just don't feel the need for it to be a constantly-online server.
TBH I don't see a reason why something as simple as a password manager needs a server, selfhosted or not. I don't get the obsession with syncing everything, so would rather stick with normal KeepassXC.
I would not be surprised if a large chunk of population can evade bans, so no surprise.
Counterpoint - the only reason I didn't degoogle earlier was because my phone simply didn't support Lineage or Divest. Chances are that whatever budget Chinaphone you have would be in the same situation. Now I bought a Pixel specifically with the intent of installing a privacy-preserving OS, but for a while most I could do was ADB-disabling Google services.
Unlike installing Linux, chances are high that a degoogled OS wouldn't work on the hardware you already have.