Re:Teamspeak 5 to be based on the Matrix protocol
by executesorder66 on Tuesday January 12, 2021 @07:45AM
(#25746084)
> Being lightweight is one of the reasons I prefer Teamspeak over Discord.
Any reason you prefer teamspeak over mumble?
Re:Teamspeak 5 to be based on the Matrix protocol
by 0x004C on Tuesday January 12, 2021 @09:12AM
(#25747115)
I just happened to setup a Teamspeak server instead of Mumble long time ago. Now it's hard enough to get friends use Teamspeak over Discord :)
Re:Teamspeak 5 to be based on the Matrix protocol
by c0l0 on Tuesday January 12, 2021 @08:56AM
(#25746899)
Imho no, except for the network effect from when you have lazy friends/users who don't want to migrate away from the product they are already using.
Re:Teamspeak 5 to be based on the Matrix protocol
by HowTheStoryEnds on Thursday January 14, 2021 @12:07AM
(#25772343)
For my group it was mumble's voice normalisation and the inability to boost or lower the volume of individual users.
Re:Teamspeak 5 to be based on the Matrix protocol
by jdellinger on Tuesday January 12, 2021 @06:17AM
(#25745339)
The current beta uses 7 processes with a total RAM of 139MB, so not as bad as some electron apps.
Old TS3 client uses 60MB.
Re:Teamspeak 5 to be based on the Matrix protocol
by johnchristopher on Tuesday January 12, 2021 @06:37AM
(#25745496)
And then we end up with unfederated networks which matrix is supposed to be all about.
Re:Teamspeak 5 to be based on the Matrix protocol
by dsr_ on Tuesday January 12, 2021 @07:10AM
(#25745786)
The point of an open source federated communications tool is that you can make your own federation if you want to, with your own policy.
Re:Teamspeak 5 to be based on the Matrix protocol
by johnchristopher on Tuesday January 12, 2021 @07:41AM
(#25746048)
Yeah, but it clashes with the mail analogy that is used to promote federation.
But what makes me wonder is the choice of words "based on matrix" instead of "using matrix". So even if you wanted you couldn't federate.
Re:Teamspeak 5 to be based on the Matrix protocol
by worble on Tuesday January 12, 2021 @08:07AM
(#25746283)
Assuming they do wish to maintain interoperability, you can use matrix while extending the base "events" that are sent to clients. So it may be that essentially Teamspeaks client/server will support the main specification "m.room" events, such as joining, leaving, adding/editing titles, etc, while also exposing their own "com.teamspeak.event" addons (which might be invites to voice channels or recordings or something specific like that), which so long as the client says "oh hey, I know those, speak them to me" will work fine, and any other client could still get the basic chat functionality.
I'm not sure how exactly this works with server <-> server federation, I've never actually looked at that spec.
https://matrix.org/docs/spec/client_server/r0.6.1#types-of-r...
Speaking of Teamspeak 5 - I hope the new client doesn't hog multiple gigabytes of RAM. Being lightweight is one of the reasons I prefer Teamspeak over Discord.