- cross-posted to:
- eticadigitale@feddit.it
- google@lemdro.id
- cross-posted to:
- eticadigitale@feddit.it
- google@lemdro.id
cross-posted from: https://lemdro.id/post/125896
July 19, 2023 An important step towards secure and interoperable messaging Posted by Giles Hogben, Privacy Engineering Director
Most modern consumer messaging platforms (including Google Messages) support end-to-end encryption, but users today are limited to communicating with contacts who use the same platform. This is why Google is strongly supportive of regulatory efforts that require interoperability for large end-to-end messaging platforms.
For interoperability to succeed in practice, however, regulations must be combined with open, industry-vetted, standards, particularly in the area of privacy, security, and end-to-end encryption. Without robust standardization, the result will be a spaghetti of ad hoc middleware that could lower security standards to cater for the lowest common denominator and raise implementation costs, particularly for smaller providers. Lack of standardization would also make advanced features such as end-to-end encrypted group messaging impossible in practice – group messages would have to be encrypted and delivered multiple times to cater for every different protocol.
With the recent publication of the IETF’s Message Layer Security (MLS) specification RFC 9420, messaging users can look forward to this reality. For the first time, MLS enables practical interoperability across services and platforms, scaling to groups of thousands of multi-device users. It is also flexible enough to allow providers to address emerging threats to user privacy and security, such as quantum computing.
By ensuring a uniformly high security and privacy bar that users can trust, MLS will unleash a huge field of new opportunities for the users and developers of interoperable messaging services that adopt it. This is why we intend to build MLS into Google Messages and support its wide deployment across the industry by open sourcing our implementation in the Android codebase.
Ah yes, another standard to fix the lack of standards. I’m sure Apple will play nicely, this time.
I’m still not over Google killing Google Talk with XMPP/Jabber support.
Won’t they be forced into by the EU and its mandate to make messaging interoperable?
at this point, the EU may as well mandate the entire device
God willing, Google can have six new apps out this year that each do a piece of what they had accomplished circa 2014.
Curious how this will interact with RCS. Hopefully it will at least get Apple to natively support an interoperable rich format
I would assume it will require RCS?
Edit: Ah, I get it.
Google is strongly supportive of regulatory efforts that require interoperability for large end-to-end messaging platforms.
If they can get laws made that require interoperability, then Apple will be forced to support RCS.
Apple’s customers aren’t asking for these kinds of upgrades to iMessage. They’re satisfied with what’s there, so the only reason Apple would change things up is because carriers are demanding it. That’s the only way this is going to move forward and to be honest it’s getting kinda sad watching Google keep trying to just shame Apple into caring. They won’t and don’t.
And to be real frank, Google doesn’t even want to run a domain registrar anymore. I’m not lining up to try out any new Google tech. They’ve lost that trust. I’d rather convince all my friends to use Signal.