OK, I upgraded to the latest Signal and it still works as an SMS client.
Kind of a twist of the knife that they are also prominently pushing “stories” in this update, which…. does not seem like it was any sort of user-requested feature.
@lucifargundam Yeah. I understand where they are coming from — ironically, I'm complaining about this in between drafts of a blog post about how sometimes you should deliberately choose to *not* implement features that people want if a sufficiently high percentage of people will use those features wrong. That's basically the whole justification for removing SMS, so you'd think I'd be in support of it, except:
1. I think SMS support was actually a core feature of Signal and they should probably lean in to UX design to minimize any potential harm rather than give up on it
2. In the same blog post I suggest that when you have a feature that some people might use correctly but a larger fraction of people might use incorrectly, you should probably still include the feature, but just make it *more difficult*. In this case adding a setting like, "Enable SMS even though it's insecure" would really help.
@pganssle sms still disabled for me on 6.2.4 (latest on Android)
@pganssle Luckily you can disable stories in the settings. First thing I did.
@pganssle
I'd rather keep sms than any 'features' developed.
There's an old passage somewhere that says something along the lines of 'The most efficient tools do only one thing- and one thing very well.'
I'm not using signal to post facebook status or to submit git patches via mms. All I want is simple, safe, secure communication. Emojis can be added after.