TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

An important step towards secure and interoperable messaging

15 pointsby trulyrandomalmost 2 years ago

3 comments

lxgralmost 2 years ago
At a first glance, this looks like a variation of the Signal protocol to me, which seems great as a message-layer solution (i.e. a successor to OTR) – as long as the idea is not to bolt it onto RCS, like OTR was bolted on to various non-interoperable messaging protocols.<p>I’m quite happy to be mostly independent from telcos and phone numbers for my instant messaging; I really don’t want to go back to the bad old days of messengers supporting only one device per account and my account and address being tightly coupled to a phone plan&#x2F;number.<p>“Google builds another messenger” is a joke at this point, but the reality of “Google delegates messaging to telcos” might just be worse.<p>Yes, iOS&#x2F;iMessage and Android&#x2F;RCS don’t interoperate and it’s very annoying, but not even Android (RCS) and Android (SMS, because there’s seemingly still uncountable edge cases disqualifying RCS in many given setups) interoperating is honestly unforgivable.
webmavenalmost 2 years ago
<i>&gt; 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.</i><p>Weeeell…<p>Let&#x27;s just say that this might also be a <i>very</i> smart move on Google&#x27;s part, a classic &quot;using Open as a weapon&quot; strategy that sidesteps their historic issues with &quot;yet another (cancelled) messaging app&quot; by baking the functionality into a lower level of their platform:<p><a href="http:&#x2F;&#x2F;www.catb.org&#x2F;~esr&#x2F;writings&#x2F;cathedral-bazaar&#x2F;magic-cauldron&#x2F;ar01s11.html" rel="nofollow noreferrer">http:&#x2F;&#x2F;www.catb.org&#x2F;~esr&#x2F;writings&#x2F;cathedral-bazaar&#x2F;magic-cau...</a><p><a href="https:&#x2F;&#x2F;www.forbes.com&#x2F;sites&#x2F;ciocentral&#x2F;2012&#x2F;04&#x2F;03&#x2F;be-wary-of-geeks-bearing-gifts&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.forbes.com&#x2F;sites&#x2F;ciocentral&#x2F;2012&#x2F;04&#x2F;03&#x2F;be-wary-o...</a><p><a href="https:&#x2F;&#x2F;blog.gardeviance.org&#x2F;2015&#x2F;12&#x2F;open-source-as-weapon.html" rel="nofollow noreferrer">https:&#x2F;&#x2F;blog.gardeviance.org&#x2F;2015&#x2F;12&#x2F;open-source-as-weapon.h...</a><p>Whether this ultimately solves the &quot;blue vs. green bubbles&quot; issue is an open question, but I suspect they&#x27;ll (eventually) at least gain some leverage by introducing an equivalent UI affordance that legitimately indicates something like more-&#x2F;less-&#x2F;insecure.
评论 #36795497 未加载
remramalmost 2 years ago
Some of us still remember Google Chat using XMPP a few years back, because &quot;interoperable messaging&quot;, and then not.