News for hackers. Stuff that matters.
Re:Beeper – Moving Forward by joshmanders on Thursday December 21, 2023 @04:35PM (#38727307)
> Google has tried literally everything to try and get Apple to play ball here.

You're framing it in a nefarious way as if Apple is flat out denying it. They didn't. They would have to LOWER security in iPhones by implementing RCS because iMessages have E2EE but RCS doesn't. Which is something all you anti-Apple people seem to conveniently leave out, because you know nobody would take it seriously if you said it.

Re:Beeper – Moving Forward by ruszki on Thursday December 21, 2023 @05:24PM (#38727944)
In the thread to which you replied, somebody mentioned that it’s possible to do that on top RCS, and Google already did it. If Apple wants to make their own encryption they can do it, nothing stops them. Interoperability would still be better, just like in the case of Google with other RCS solutions.
Re:Beeper – Moving Forward by riscy on Thursday December 21, 2023 @05:35PM (#38728080)
Please explain how interoperability between messaging apps is possible if two different, proprietary E2EE schemes are used atop RCS.

Google's interop "solution" with the Samsung messages app is by not using encryption. Apple has that same level of support coming to iOS next year, and has also announced plans to work with GSMA on adding standardized encryption to RCS.

Re:Beeper – Moving Forward by ruszki on Thursday December 21, 2023 @05:49PM (#38728197)
I like that you put Google’s solution into apostrophes, while Apple’s current solution has the same problem, and even more. But I’m glad that we agree.
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?

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.
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.

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.
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.
Re:Beeper – Moving Forward by xg15 on Thursday December 21, 2023 @05:17PM (#38727857)
Well I guess then they should let other people interop with iMessage directly, so the E2EE can be kept.
Re:Beeper – Moving Forward by shawnz on Thursday December 21, 2023 @05:31PM (#38728024)
the iPhone messages app already supports unencrypted SMS though