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 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.