I don’t understand why they continue to do this? Apple’s already working on adding E2EE to the RCS Universal Profile and implementing it into iMessage, so the need for a “blue bubble” in Android is going to become moot.
I get the whole thing about interoperability, but when your app’s business model revolves around charging people money to access a glorified exploit (Apple themselves stated this was the case, but you can easily verify this by looking at the source code of Beeper’s own PoC), to then follow up with more hacks and workarounds that will inevitably get patched, the sustainability of such an operation becomes dubious.
Various Apple statements on the matter, I’ll link to the r/UniversalProfile post celebrating it. (As it turns out, the post did not actually say anything about E2EE. It’s a statement that’s been shared on several different tabloids though.)
It’s the most logical approach to achieve interoperability because, while Google RCS already supports E2EE, it is pretty much the antipode of interoperability: only Google and Samsung are allowed true access to gRCS’s APIs. Apple being additionally granted access would effectively establish a messaging duopoly, as there would be no reason to use anything other than Google Messages and iMessage. There’s a reason why these APIs don’t exist in the AOSP.
I couldn’t find a non-tabloid source or a direct link to an Apple statement in the moment, but that doesn’t mean they’re not going to do it. It’s already been reported by the media as “stated-by-Apple”, and if that’s not the case I’m sure Apple will gladly rectify things themselves.
I don’t understand why they continue to do this? Apple’s already working on adding E2EE to the RCS Universal Profile and implementing it into iMessage, so the need for a “blue bubble” in Android is going to become moot.
I get the whole thing about interoperability, but when your app’s business model revolves around charging people money to access a glorified exploit (Apple themselves stated this was the case, but you can easily verify this by looking at the source code of Beeper’s own PoC), to then follow up with more hacks and workarounds that will inevitably get patched, the sustainability of such an operation becomes dubious.
Where did you see about adding E2EE to RCS?
Various Apple statements on the matter,
I’ll link to the r/UniversalProfile post celebrating it.(As it turns out, the post did not actually say anything about E2EE. It’s a statement that’s been shared on several different tabloids though.)It’s the most logical approach to achieve interoperability because, while Google RCS already supports E2EE, it is pretty much the antipode of interoperability: only Google and Samsung are allowed true access to gRCS’s APIs. Apple being additionally granted access would effectively establish a messaging duopoly, as there would be no reason to use anything other than Google Messages and iMessage. There’s a reason why these APIs don’t exist in the AOSP.
Yeah, I didn’t think they said E2EE. Just RCS to be able to say, “we did it!”
https://appleinsider.com/articles/23/11/16/apples-flavor-of-rcs-wont-support-googles-end-to-end-encryption-extension/amp/
I couldn’t find a non-tabloid source or a direct link to an Apple statement in the moment, but that doesn’t mean they’re not going to do it. It’s already been reported by the media as “stated-by-Apple”, and if that’s not the case I’m sure Apple will gladly rectify things themselves.
deleted by creator
Apple publicly announced that RCS is coming. I don’t get why they would need pressure to do something they have already announced.
Pressure shortens that timeline significantly IMO, similar to what happened with USB-C
deleted by creator
deleted by creator