Hacker News Reader

Comment by pabs3 | Hacker News Reader

IIRC with RCS, carriers don't run the infrastructure, Google does.

That’s not how it’s supposed to work. It’s a federated system with each carrier supposed to run things for their customers.

Why does it work today? After years of begging Google gave up and put all their users without carrier support (basically everyone) onto a Google RCS instance.

Despite how the article tries to portray things in many ways it’s iMessage but worse. With Google running everything it might as well be proprietary. And it lacks full E2E encryption.

Things probably would’ve been better off if Google had just stuck to their own private protocol and used that instead, perhaps opening it.

Telstra kicked off RCS in Australia, but only on their network, then Google did one for everyone else, but it doesn't work with Telstra AFACT.

Vodafone has this business RCS page:

https://www.vodafone.com/business/carrier-services/messaging...

and they "launched" in 2018, but from what I can tell still no-one is using it.

There's a lot of confusion around it.

> from what I can tell still no-one is using it.

> There's a lot of confusion around it.

The story of every feature introduced by telcos in the last 100 years that goes beyond voice calls or text messages.

I seem to recall a similar picture when SMS was introduced. For many years, you couldn't text people outside your phone network.

It's not just on the telcos, Android fragmentation as a whole makes implementing new network features an uphill battle. VoLTE is an absolute mess (on Android) if your build doesn't have settings for your carrier. Google doesn't sell the Pixel in my country, so the only way to enable VoLTE here is to root your device. This is only going to get worse with carriers sunsetting 3G networks - anyone roaming on a Pixel in such a country won't be able to make calls, even to emergency numbers.

Reply on news.ycombinator.com