Hacker News new | past | comments | ask | show | jobs | submit login

>I'm not suggesting another competing platform. I'm suggesting an already-widely-deployed platform (RCS) that is standardized, has been around since 2008 or so (older than iMessage!), and is the actual real elevation of SMS, not an Apple-proprietary protocol.

The RCS Universal Profile is the first standardized version by the GSMA and came out in late 2016.

Google's RCS usage has primarily been via Google's own hosted implementations because of poor carrier adoption. Verizon AFAIK is planning to have RCS deployed this year.

Also AFAICT the e2e extension is not a standard but is Google-specific and currently exclusive to their Messages app. It also has several inferior technological, privacy, and UX impacts to other systems (such as only working for 1-to-1 chat, or requiring out-of-band verification code comparisons to guarantee the encryption isn't compromised).

It also is not a protocol evolution of SMS - its similarity is mostly that it like SMS was standardized through the GSMA. I also do not believe that the GSMA mandates its usage "instead of" SMS - it is meant to sit alongside SMS.

> That's a huge pain in the ass. Not all of my friends have Signal, and I'm tired of evangelizing. Not all of my friends have WhatsApp, and I'm not interested in evangelizing a Facebook property.

There's zero chance that RCS will replace Signal or WhatsApp or Telegram. It also won't replace SMS, at least this decade. It's just going to be Yet Another Option.




Google not opening up RCS to other applications is really annoying - I used to have a text messaging app I loved with TONS of customization and now I am basically forced to use googles damn messages app. It is the same shit as Apple is doing




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: