836
get new phone (slrpnk.net)
submitted 2 years ago by [M] to c/enshitification@slrpnk.net
238 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (1 child)

[...] Or so on and so forth, which is already a terrible UX worthy of criticism.

I mean... You get what you get with the provided infrastructure. If you want decentralized storage, this is what you get. I think it's a good thing. The UX is fine from my perspective. I'm not using WhatsApp for sensitive data or conversations that I need to save indefinitely. So for that purpose, it's good enough, UX wise. I use the web app all the time, too.

It’s not stored on any server

It is stored as an encrypted blob on your gdrive. It asks you about it on every login. Otherwise, how would you recover your chat history if you lost or changed your phone.

That's different. That's not what I mean by your messages being "stored on a server". What you're talking about is an incremental backup sync. It's not where messages are fetched when you receive messages while chatting. Not to mention it's entirely optional last time I checked. I have it disabled and it doesn't nag me about it. 🤷‍♂️

The whole security aspect is surely an issue regardless of app, if the perpetrator is looking to steal your data rather than your hardware. If they have your phone, and bypass the lock screen, then they have your 2FA app and everything. You're fucked regardless of app.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    That’s different. That’s not what I mean by your messages being “stored on a server”. What you’re talking about is an incremental backup sync. It’s not where messages are fetched when you receive messages while chatting. Not to mention it’s entirely optional last time I checked. I have it disabled and it doesn’t nag me about it. 🤷‍♂️

    This "incremental backup" is literally the same thing that's sitting on your phone and from where the messages are read from and where new messages are appended to. So it's technically is being read from there, e.g. if you receive a message, uninstall whatsapp before opening reading it, re-install and restore from backup, you've technically got a message from google's server. Secure messengers are not space magic, it's just a database, probably even just JSON file encrypted with some homebrewn public key crypto derived from a seed phrase. The only difference between WA and other messengers is that Facebook is for some reason very adamant about keeping it at your phone, and also shifts the burden of storing messages to google rather than themselves for some reason.

    The whole security aspect is surely an issue regardless of app, if the perpetrator is looking to steal your data rather than your hardware. If they have your phone, and bypass the lock screen, then they have your 2FA app and everything. You’re fucked regardless of app.

    Nope. I can literally hand you my unlocked phone and you wouldn't be able to do anything malicious with it because everything is behind passwords, passkeys, and fingerprint verifications. Last one, not a big fan of, but it's the only option for some of the apps. You can try some advanced techniques like memory dumping and scavenging keys from there, but if you're too slow and/or I get to any other device first (even not mine), then there wouldn't be anything to recover from it at all.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    This "incremental backup" is literally the same thing that's sitting on your phone and from where the messages are read from and where new messages are appended to. So it's technically is being read from there, e.g. if you receive a message, uninstall whatsapp before opening reading it, re-install and restore from backup, you've technically got a message from google's server.

    🙄 I don't know why you're making up these crazy scenarios. This is not the same. This scenario that you constructed is the same as restoring from a backup. It's not at all "technically the same" as "receiving" the message from Google, in the normal way that the app "receives" messages. It's not the same code path. It would go via the backup code path in your example, and it would have no idea whether or not it was an old or new message. It is however practically the same, given that you "have all your messages in the end". But please stop dragging this backup thing further – you seem knowledgeable enough that this is not technically the same thing. Let's move on from this point. 👍

    Nope. I can literally hand you my unlocked phone

    Oh, okay, yes, that is much different, sure. If you just hand them your unlocked phone. That's not how I understood the scenario at first though. I thought you said they somehow bypassed the lock screen, indicating to me that they would somehow be able to do so with everything else behind the phone's security system as well (e.g. they know your PIN, have a way to unlock using your biometrics, or something more advanced). So yeah, if we're changing it to just handing it to them now, that's different of course.

  • permalink
  • fedilink
  • source
  • parent