> 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.
Weeeell…
Let's just say that this might also be a very smart move on Google's part, a classic "using Open as a weapon" strategy that sidesteps their historic issues with "yet another (cancelled) messaging app" by baking the functionality into a lower level of their platform:
Whether this ultimately solves the "blue vs. green bubbles" issue is an open question, but I suspect they'll (eventually) at least gain some leverage by introducing an equivalent UI affordance that legitimately indicates something like more-/less-/insecure.
> > 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.
Are they talking about open-sourcing the whole messaging app, or only the MLS library used within it?
It’s not even a matter of open-sourcing the messaging app: Without a viable backend implementation (supporting federation etc.), there is no way to communicate!
Google seems to be stubbornly pushing RCS, but it’s clearly not working at least internationally.
Are they talking about open-sourcing the whole messaging app, or only the MLS library used within it?