This is a really terrible idea, and the reasoning doesn't make much sense. The three reasons given are all the same reason which is "users aren't sure whether t

This is a really terrible idea, and the reasoning doesn't make much sense. The three reasons given are all the same reason which is "users aren't sure whether they are sending SMS or signal messages" and is purely a UX problem. Reason 1 and 2: Users can be confused by whether a message is SMS or Signal and this is bad for security, backed with "there's only so much we can do on the design side"...really? At what point do you sacrifice the convenience of the masses in order to get through to people who don't understand that a message that says "SMS" on it is sent over SMS? Hell, turn SMS bubbles bright red or something, that would be better than removing the feature. Reason 2: Users can be confused by whether a message is SMS or signal and thus end up incurring charges - I thought about this for 5 seconds and came up with a solution - ask the user whether they ever want to send SMS through the signal app when they first open it and respect that preference. Make it a setting. Boom, if you are using signal you know you're going over data. Or is the response to that that users are too dumb to understand it? I'm positive there is a good solution here. This decision just doesn't make any sense and it's probably obvious to the people working on signal that it doesn't make sense, I wonder what the decision process looked like here.