RCS doesn’t have a cross-platform end-to-end encryption solution. For cross-platform communication, cross-platform 3rd party solutions such as Signal work well.
I 100% agree that Apple wrong for not supporting RCS (and I am an iPhone user). However, I personally choose to only use E2E for my communication be that iMessage or Signal.
Oh, I agree and would love to do the same. However, moving any of my family who currently uses Android over to any other platform is impossible. I can’t tell my wife I won’t text her anymore unless she uses it. That won’t go over well hahah
Where possible, I use encrypted communication, but if doing so would result in me cutting off a friend or family member, I won’t do so.
However, I would love to be able to text Android users without crappy quality and the other limitations of SMS/MMS.
I don’t find #Signal or #Telegram (which is worse, it’s basically a honeypot) to be particularly secure, but I don’t see anything other than something like those platforms catching on with the masses as a sort of #USA-centric #Whatsapp-style replacement for text messaging.
Both #Apple and #Google need to come up with a consensus on the successor for #MMS, or else I could see another platform or app replacing both.
There are two legitimate concerns about Signal: they use real phone numbers as identifiers, and you have to trust Signal as the server operator as they don’t allow their client to be used with other servers. While the server software is also open source, you have to trust that they’re running the same version in production.
I agree; however, the second point I don’t see as Signal specific. In any service, how do you verify that a server is running unmodified open source code? For the vast majority of people, they are also depending upon the client being unmodified.
If you could run your own Signal instance, then that could help alleviate concerns of bad faith operators. That’s what Session is essentially (started as a fork of Signal): https://getsession.org
RCS doesn’t have a cross-platform end-to-end encryption solution. For cross-platform communication, cross-platform 3rd party solutions such as Signal work well.
RCS would still be a benefit to incorporate without the E2E solution, as it would improve nearly every other aspect of communication over SMS/MMS.
I 100% agree that Apple wrong for not supporting RCS (and I am an iPhone user). However, I personally choose to only use E2E for my communication be that iMessage or Signal.
Oh, I agree and would love to do the same. However, moving any of my family who currently uses Android over to any other platform is impossible. I can’t tell my wife I won’t text her anymore unless she uses it. That won’t go over well hahah
Where possible, I use encrypted communication, but if doing so would result in me cutting off a friend or family member, I won’t do so.
However, I would love to be able to text Android users without crappy quality and the other limitations of SMS/MMS.
@RandomBit @jmcs I prefer #Matrix.
I don’t find #Signal or #Telegram (which is worse, it’s basically a honeypot) to be particularly secure, but I don’t see anything other than something like those platforms catching on with the masses as a sort of #USA-centric #Whatsapp-style replacement for text messaging.
Both #Apple and #Google need to come up with a consensus on the successor for #MMS, or else I could see another platform or app replacing both.
What security issues does Signal have?
There are two legitimate concerns about Signal: they use real phone numbers as identifiers, and you have to trust Signal as the server operator as they don’t allow their client to be used with other servers. While the server software is also open source, you have to trust that they’re running the same version in production.
I agree; however, the second point I don’t see as Signal specific. In any service, how do you verify that a server is running unmodified open source code? For the vast majority of people, they are also depending upon the client being unmodified.
If you could run your own Signal instance, then that could help alleviate concerns of bad faith operators. That’s what Session is essentially (started as a fork of Signal): https://getsession.org
With e2e encryption, you don’t need to trust the server, you only need to trust the clients.
@RandomBit I’m not aware of exactly what issues #Signal has, but I know it’s centralized so I’m not a big fan of that
Sort of off topic but are you replying from Mastodon?
Yes, it’s not ideal. Decentralized key distribution seems to be a intractable problem for mass adoption.
@RandomBit That said if #Signal ever supports #RCS I’d strongly consider getting it, since half my siblings are on #RCS