Correct Apple is & iMessage is under investigation. I wasn't clear....clearly
End to end encryption. Less spam. Identity verification. More consistent feature adoption.
and nowhere does the text say no end to end encryption is't protected. it's for basic interoperability, the platform is free to have all the uneque features they want. it will just no longer be possible to rely on a big user base as the sole factor.
Re: the last paragraph. Europe confuses me sometimes. Let me put it this way: the ship has probably sailed on Europe being a hegemonic power, economically and politically. For one, it wouldn’t be popular in the developing world, especially in regions that were European colonies at one point in time. They’d just have no desire to work with hegemonic Europe. For two, hegemonic power generally requires military power, and the US is effectively Europe’s military (considering how little of their expected contributions the EU member states pay to NATO, the US is effectively bankrolling their national defense). Economically and militarily, they’re clearly client states of the United States, no getting around that. Culturally, they consume American media at a high rate, too. (Basically, their domestic media can be more art scene driven because the mass market media is imported, localized American content.) So, strong cultural, military, and economic ties bind the US and the EU, but the EU tries so hard to assert its independence to the US.
Pure fantasy. E2E encryption can't be preserved if you can't verify the endpoints.
By definition. That’s what makes it End to End, after all. Can we be sure that the message arrives at its destination in a usable state after arriving at the destination service and user? Can we audit every stage along the data path as it moves across different companies’ systems? If not, then we can’t trust claims of end to end encryption. It’s much easier when it’s basically “encryption at rest, encrypted with your public or private key”, as it is on iMessage and WhatsApp.
And on what basis do you do that? You can always verify the end point.
Everyone else is already using RCS.Simple solution is to just require all EU carriers to adopt RCS. Sure, those carriers will have to pay to have their infrastructure updated for no financial benefit, but EU regulators don’t exists to make sure that what they’re requesting is financially viable.
Well, I think the media codex that MMS uses doesn’t handle large images or videos well. It converts videos to the old 3gp format, and images, it compresses them worse than JPEG. But for the kind of stuff you’d share over email, it works well.
No, we don’t. We’re talking about digital markets. As far as the EU is concerned WhatsApp and their parent company can go bankrupt, nobody cares. The question is does Apple’s iMessage lock-in hinder customers and competitors to freely chose what’s best for them? For example can you change the default messaging app on iPhone and achieve the same integration? Can you use another payment service via iMessage?
Sigh. Once again, you don't understand what your linking to. That method in no way solves the problem that I referenced.And on what basis do you do that? You can always verify the end point.
Combining the symmetric-key and DH ratchets gives the Double Ratchet.
unless you want to say apple imesage is so insecure to compromise it
Specifications >> The Double Ratchet Algorithm
The Double Ratchet algorithm is used by two parties to exchange encrypted messages based on a shared secret key.signal.org
Oh ok that makes sense. I just hadn't run into many issues personally and heard some people mention it on the thread.
Once again if you mean a 100% secure? Then E2E encryption is a fantasy on iMessage as well.
medium.com
Again, you are linking to something that does not address the concern that I referenced.Once again if you mean a 100% secure? Then E2E encryption is a fantasy on iMessage as well.
There multiple ways to secure the connection with different levels of convenience for the end user.
Enhancing Signal’s End-to-End Encryption Algorithm Eliminating Man-in-the-Middle and other…
In this article, we will briefly describe the shortcomings of Open-Whisper System (Signal)’s end-to-end encryption algorithm and why we…
We are talking about service interoperability, not multi-service clients.
So what is your actual concern? What issue is it your identifying that exist in an interoperable system and not inherently in e2ee messaging?
And in what way is this different with your question to security? This isn’t a multi service client. I can send or receive iMessage messages with it or any other message.
