Matrix could’ve implemented it with classic TURNS for a while now so the feature at least is there for those needing it, but they dug their own hole instead and focused so hard on their idea of a protocol they created software that hardly can do anything, and what is should be able to do it does really badly. Also for some reasons it was more important to throw away he concepts of “Communities” and build… “Places”. Now Element is a convoluted mess that <Error Decrypting Second Part of this Message>
Yeah, the people behind it always seemed to be more interested in getting corporate funding and thus gave corporations more what they wanted/needed instead of typical users and mods. This is part of the reason why I’m no longer interested in matrix main and more hard forks of it.
To my understanding they’re pushing those TURN connections through your home instance though? Wasn’t that the whole reason it takes so phenomenally long?
Otherwise implementing WebRCT with TURN would be rather easy, there are ready-to-use modules and frameworks to do so in basically any language. Whatever it is that’s wrong with the teams behind Matrix, it causes Matrix (especially when used with Element) to be just awful and buggy.
Matrix could’ve implemented it with classic TURNS for a while now so the feature at least is there for those needing it, but they dug their own hole instead and focused so hard on their idea of a protocol they created software that hardly can do anything, and what is should be able to do it does really badly. Also for some reasons it was more important to throw away he concepts of “Communities” and build… “Places”. Now Element is a convoluted mess that <Error Decrypting Second Part of this Message>
Yeah, the people behind it always seemed to be more interested in getting corporate funding and thus gave corporations more what they wanted/needed instead of typical users and mods. This is part of the reason why I’m no longer interested in matrix main and more hard forks of it.
Matrix uses TURN, and the Matrix protocol is not used for carrying voice/video.
Element is an independent client developed by Element, and not part of the Matrix protocol.
To my understanding they’re pushing those TURN connections through your home instance though? Wasn’t that the whole reason it takes so phenomenally long?
Otherwise implementing WebRCT with TURN would be rather easy, there are ready-to-use modules and frameworks to do so in basically any language. Whatever it is that’s wrong with the teams behind Matrix, it causes Matrix (especially when used with Element) to be just awful and buggy.
The legacy jitsi-based rtc used turn, and so does matrixrtc I believe. I haven’t tried it myself, though.