451–460 of 460 posts
Earlier quoted context omitted.
iOS to iOS works Android to Android works iOS to/from Android does not work stolen phone to new phone does not work :)
> stolen phone to new phone does not work :) I'm curious about that, has this been tested by someone who "steals" the phone, and tries to migrate before the actual phone owner even realizes?
If Signal is offering pay-for-media-storage, it would be nice to be able to pay to send full-resolution media. I’m a photographer and every image sent via Signal that isn’t zipped first is TOTALLY DESTROYED by silent recompression. https://sneak.berlin/20210425/signal-is-wrecking-your-images... Also, the donation spam in Signal doesn’t let me donate Mobilecoin from the wallet right inside Signal. What’s the point of…
"Grift for thee, but not for me"
Or just GPG encrypt your messages and store it on some cheap shitcoin's blockchain for free forever storage.
Earlier quoted context omitted.
Not if you run the GrapheneOS variant of Android.
I would love to but my banking apps only work on Google Android.
https://privsec.dev/posts/android/banking-applications-compa...
@Signal devs: any reason that the only two options for backup are now "locally" (flexible, but only solves for some use-cases) or "to Signal's special servers" ( not flexible; might be legally impossible for many users to enable)? Because it seems to me that, for much of Signal's (often paranoid) audience, they'd much rather use one of the backup/sync providers they've already verified trust of, than have to addition…
I wonder if those folks are the ones actually asking for backups. Personally I couldn’t give a shit about my messages from more than a week ago and part of that has to do with privacy. People concerned with privacy might also be more likely to have disappearing messages on which is the exact opposite of a backup. I honestly wonder who this is for exactly. From reading other threads, are people using this as their primary media backup basically?
@Signal devs: any reason that the only two options for backup are now "locally" (flexible, but only solves for some use-cases) or "to Signal's special servers" ( not flexible; might be legally impossible for many users to enable)? Because it seems to me that, for much of Signal's (often paranoid) audience, they'd much rather use one of the backup/sync providers they've already verified trust of, than have to addition…
> Because it seems to me that, for much of Signal's (often paranoid) audience, they'd much rather use one of the backup/sync providers they've already verified trust of, than have to additionally trust some new backup service provider. I wonder if those folks are the ones actually asking for backups. Personally I couldn’t give a shit about my messages from more than a week ago and part of that has to do with privacy.…
Earlier quoted context omitted.
"I consider it a bug because I really want this feature" does not change the fact that it is a feature. > As an example, a piece of code sending authentication credentials in plain text across the internet might in isolation be considered free of bugs. This is not a good example. It's almost certainly a security issue. Unless you have a threat model where you absolutely don't give a shit about it, but we're not in 20…
Today I learned that some people consider unexpected data loss a feature, and that removing such a "feature" is in fact the same as adding a new feature. It's newspeak all in the software world. A first for everything I suppose.
I did not say that, and I am not sure if you genuinely do not understand or if you do it on purpose. Let me try one last time with simple constructs:
The lack of backup is not a feature. The lack of backup is a missing feature. The lack of backup is not a bug.
> and that removing such a "feature" is in fact the same as adding a new feature.
I have no clue what you are trying to say here, it's just gibberish.
Earlier quoted context omitted.
iOS to iOS works Android to Android works iOS to/from Android does not work stolen phone to new phone does not work :)
> stolen phone to new phone does not work :) I'm curious about that, has this been tested by someone who "steals" the phone, and tries to migrate before the actual phone owner even realizes?
Earlier quoted context omitted.
Signal has done a very poor job of calling out that you can optionally connect your old and new phone via cable; the transfer will be much more stable and quick. (No, this does not really help if you're one of the TouchID holdouts on an older SE)
Wow! I didn’t know this! So you’re saying that instead of using slower and potentially unreliable WiFi, I could just use the iPhone charging cable to connect two iPhones and start the Signal transfer feature? Is this documented anywhere? Thanks.
This looks brilliant. I just hope they make it easy to do test restores. In particular, I want to test restore without perturbing my main device. Let me restore using the secret key on a new device. When I install Signal on a computer it won't show me message history. Will backups allow me to view _all_ my message history on a computer? A big screen is very helpful for browsing lots of messages.
Hi there, Signal dev here. You can sort of do this! You can restore on your new device, and while you will be unregistered on your old device, all of the data is still there. So if you see that something is amiss on the new device, you could re-register on your old device and you'd be right back where you started. This is actually one of the ways we test the feature with our own personal data.
Testing backups is important, separate of when you try to restore. It sucks hard to find out your backup is bad only when you go to need it. I highly recommend the quick, beautiful, and informative Tao of Backups.
Mike Nahas, Designer of Par2 file format