Signal-android: Force SMS for specific user?

[mseddon]

A friend of mine has stopped using signal without deregistering. Unfortunately that means every time I attempt to send them a message, I have to remember to manually move from "Signal" to "Insecure SMS" messaging for them to get my messages at all. Is there a way that I can override this setting for that number specifically?

[riyapenn]

Best thing is to ask your contact to unregister: https://whispersystems.org/textsecure/unregister/

[mseddon]

Would it not be possible to add a feature where one sets the default behaviour to insecure until the contact sends a new signal message? I wouldn't mind it being a cumbersome process.

[mseddon]

The reason I'm suggesting this is now I have to make _them_ do something to solve _my_ problem, which doesn't seem to be the right solution at all! (and for those who have rejected Signal for other reasons, will merely drive them further away from the app).

[TxHawks]

+1 on this.

One should not be dependant on someone else's behavior.

[agrajaghh]

@TxHawks Please don't bump issues:
https://github.com/WhisperSystems/Signal-Android/blob/master/CONTRIBUTING.md#dont-bump-issues

[jnns]

Please consider reopening this issue as there's another reason for permanently chosing the method of transportation:

In case my contact disabled mobile data for a prolongued time (roaming for example), I have to manually switch to sending them an SMS instead of a Signal message every time I reopen the conversation window. This is very cumbersome and most of the time I forget to do this in the first place and only notice it because no answer is received.

[2-4601]

This is very cumbersome and most of the time I forget to do this

Now imagine the opposite. Someone could also forget to switch back to Signal transport and consequently find themselves in a situation where they have sent multiple unencrypted messages unintentionally.

reason for permanently chosing the method of transportation

There's already an issue for this #2285. But please only comment on it if you have relevant new information to add (see the remark two comments above).

[ArmEagle]

Good point 2-4601. But wouldn't it be better to detect on the receiving end that an insecure message was received, while data (and secure connection to the system) is available? People give valid reasons why temporary insecure messages are wanted. And this seems like a good detection to me.

[signaldefaultmessage]

Many of my contacts have got new phones and not installed signal yet, many many messages have never been delivered. Worst is when I get an sms from them and quickly reply it sends as encrypted so they think I've just ignored it. Had some pretty important business stuff lost over this.

When I tell them why they get angry at signal and are less likely to reinstall on their new phone.

Needs a simple option of "set default behavoir for this contact to unsecured"

[jefftrull]

Please consider re-opening this bug. I am evangelizing Signal to my friends, and a handful of them tried it but abandoned the effort. Telling them they need to go and do something on a website somewhere just to make it easier for me to talk to them is a non-starter - to them, "not Signal" is _normal_ and I'm the one who needs to adapt, not them. This is a real UX issue and will limit adoption.

Either this proposal (mark users "insecure transport only") or #2285 should be implemented; I personally prefer this one.

[z1chickentender]

As many others have stated here and elsewhere, this issue has caused a number of users I know to simply stop using Signal. I've given up asking them to deregister - many just don't care any longer so now it is a problem for me and me only that is not solvable currently. I am frankly on the verge of deregistering myself - at first it was just an occasional nuisance but it's become a genuine time waste cumulatively.