Hacker News Reader

I understand the desire to just use the default app. I feel the same for most of the stuff I use.

However, being based on standards is more like being based on the lowest common denominator. Moxie describes the issue pretty good in his post where he explains why signal is not federated (any more):

https://signal.org/blog/the-ecosystem-is-moving/

When talking about things like encryption, RCS isn't that much better, it seems. Correct me if I'm wrong, but encryption is optional for the implementors. That doesn't seem to make it secure by default.

And it's also not Google trying to push to open standards. In the past, Google made multiple attempts to get their own iMessage and did not succeed:

https://www.androidauthority.com/rcs-google-3090142/

It feels like the campaign for RCS ist judt a PR campaign against apple.

Don't get me wrong, I think SMS is dated and I think it needs a replacement with something more modern and open that is not owned by a private company.

I fully agree the best outcome here would be a cross-platform, E2EE standard supported as the default across a variety of platforms. (Where iMessage would be a great option if Apple would play ball.) I'm just not holding my breath...and in the absence of that the best I could think to do is explain to whoever would listen why they can take action on their own behalf and that of their community.

I think the only serious RCS client at this point is Google Messages, which defaults to E2EE when possible (i.e., both clients are Google Messages). All of the major US carriers have started shipping Google Messages by default. There are other clients like Samsung Messages and whatever crap carriers have tried to implement themselves, but It seems like they'll phase out.

As far as I can tell, Google Messages defaults to E2EE when possible when RCS is enabled, but RCS is disabled by default. Which basically means 80% of users don't have it turned on.

That's true. My reply was in the context of RCS being enabled, I guess.

Although I do think Google Messages will prompt new users to enable RCS. iMessage also isn't enabled by default as far as I'm aware.

> I think in the end we need a cross-platform messaging protocol that replaces SMS/MMS that is not reliant on a single app vendor, provides end-to-end encryption and will be supported by mobile network providers.

Except for ".. will be supported by mobile network providers.", doesn't Jabber/XMPP already fulfill all of that?

Also, I'm not sure what you mean by support by mobile network providers.

TBH I don't know the last part either. I just see it being said time and time again that I have started to assume it is true.

But I do find the idea weird that they would jump through the hoops for it unless there is a major reason for it. Like we (US) had unlimited SMS a while ago that I think also helped.

I wonder what would have to happen for iMessage to get adopted as a standard, or a similar standard to replace it. It's such a great technology, it's a tragedy that Apple has an iron grip on it.