Beeper – Moving Forward

Re:Beeper – Moving Forward by nicce on Thursday December 21, 2023 @05:54PM (#38728249)

> In the thread to which you replied, somebody mentioned that it’s possible to do that on top RCS, and Google already did it

Google made a copy of iMessage since it is closed source and can talk to only to the same app. How is that better?

[ Parent | on HN ]

Re:Beeper – Moving Forward by ruszki on Friday December 22, 2023 @01:32AM (#38731547)

I don’t know what you talk about, because both can talk to whatever they want, because both support SMS.

[ Parent | on HN ]

Re:Beeper – Moving Forward by nicce on Friday December 22, 2023 @02:10AM (#38731739)

Then there isn’t issue with iMessage either?

But you know what I mean - E2EE of Google Messages is closed solution.

[ Parent | on HN ]

Re:Beeper – Moving Forward by ruszki on Friday December 22, 2023 @02:47AM (#38731947)

Both have issues. iMessage has problems with interoperability, RCS has problems with requirement of operator support.

[ Parent | on HN ]

Re:Beeper – Moving Forward by jacksontrom on Friday December 22, 2023 @04:11AM (#38732404)

Google is still working on the standard and adding features to it. If their previous statement is true, they will open source it after that.

[ Parent | on HN ]