Here is a more official-looking statement: https://community.teamspeak.com/t/beta-signup/13749/50
> We use the Matrix protocol only for the messenger part. The rest does not require a different TeamSpeak server.
> We use the Matrix protocol only for the messenger part. The rest does not require a different TeamSpeak server.
Makes sense but it would have been nice to have been fully open source-based.
Matrix also has its own voice/video, but it's not considered entirely ready for prime time yet, hence the Jitsi embeds.
We embed Jitsi for voice/video conferences, but we're experimenting more and more with native Matrix conferencing over the course of this year.
This is rather unusual for a commercial service
Of course then leadership got to it :'(
That would have been an actual strategy, and probably would have worked, but from what I could tell they just sort of fumbled around without really committing.
As I recall, the Embrace was half-hearted, the implementation was pretty standard with no Extensions, and they never really got around to an Extinguish phase, they eventually just phased out support for XMPP clients at all.
The only way I think Google's incoherence of multiple overlapping stabs at messaging over many years makes sense is as internal maneuvering and jockeying for position among execs playing chess with the various engineering teams and end users as pawns.
ISTR that they did back off of XMPP support in Google Talk to some extent a bit before that last move. Something about not allowing incoming connection requests from non-Google accounts by default IIRC.
Are you sure you're not thinking of Twitch?
Twitch, on the other hand, did used to use a very heavily customized version of IRC for it's chat. Not sure if it still does.
I used to use custom desktop clients where the chat was basically just an irc client that automatically joined whichever Twitch Stream I was watching.