this post was submitted on 24 Jun 2023
78 points (96.4% liked)
Asklemmy
43963 readers
1290 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I dropped it when they decided to get rid of SMS. I don't want to be treated like I can't be trusted to be responsible for my own privacy and security. I understand the difference between an SMS and an encrypted Signal message and was fully aware of which contacts had Signal and which did not have it.
In my opinion they should have disabled SMS by default and made it an option with warnings to enable in the settings. They had already been doing borderline questionable things with crypto and the stories that I did not want in a messenger app... this was the straw that broke the camel's back for me.
I'm patiently waiting for a decent fork of Signal with SMS enabled, or a decent open source RCS client... unfortunately I landed on Google Messages for now.
Correct me if I'm wrong, but I belive the reason why SMS was dropped was because of the unreliable interaction between two endpoints: If you're communicating with a contact over RCS in Google messages, and you'd send them a message over signal- they'd receive an SMS. But throttling reply would be over RCS and signal wouldn't be able to display that since there isn't an open API for signal to interact with RCS messages. So the whole reason to drop SMS support was due to inconsistencies of how messages in androids would be handled.
Basically, Signal could have implemented RCS messaging themselves, making them the de facto iMessage replacement on Android, but they chose not to so that their devs could instead spend their time building NFTs into their platform or whatever the next shiny bauble is.
I still use Signal for lack of a credible alternative but dropping SMS support in favour of NFTs and Stories was fucking dumb. They need to focus on being the best messaging platform first, then focus on expanding into other markets and functionality.
That would have been great, except Google doesn't provide an API for developers to use RCS in their own apps like they did with SMS. Google's basically forcing everyone (long term) into their messaging app, which I suspect will eventually be the "iMessage" of Android since there wont be any alternative "texting" apps.