Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(deleted) #8107

Closed
MyNameIsJulian opened this issue Jan 11, 2019 · 6 comments
Closed

(deleted) #8107

MyNameIsJulian opened this issue Jan 11, 2019 · 6 comments

Comments

@MyNameIsJulian
Copy link

MyNameIsJulian commented Jan 11, 2019

(deleted)

@nadonomy
Copy link
Contributor

(Removing the redesign label as this issue is completely independent of the redesign.)

@nadonomy nadonomy removed the redesign label Jan 11, 2019
@nadonomy nadonomy changed the title Redesign: Remove centralization (Jitsi) Remove centralization (Jitsi) Jan 11, 2019
@MazeChaZer
Copy link

MazeChaZer commented Jan 11, 2019

You can host Jitsi yourself (it's open source) and configure Riot to use that instance. I don't see how the use of Jitsi enforces any kind of "centralization". Matrix is not peer-to-peer, it's federated, meaning you can choose which servers to use and all servers are interoperable. The use of Jitsi doesn't break that. FYI, group calls where very unstable before Jitsi was introduced, so there is a reason they are not peer-to-peer anymore.

@MazeChaZer
Copy link

Yeah I guess if the Matrix server would provide the location of the Jitsi server this would solve the problem, right? This is how it already works with Synapse and the TURN server if a relay for WebRTC calls is needed. You install your own TURN server and configure Synapse to use it. Would be great if one could configure the Jitsi server on the homeserver and all clients adapt automatically 👍
I'm with you on this, I think it's bad that all group calls go over https://jitsi.riot.im/ unless you reconfigure your client. Especially because this configuration is tedious and has to be done at compile time. I just think that Jitsi itself isn't the problem, more the way it's integrated into the system.
Also, this is a duplicate of #7711

@xuebaxuebaxueba
Copy link

xuebaxuebaxueba commented Apr 27, 2019

Please consider that the way this Jitsi thing is currently implemented somewhat subverts the trust model that people naturally tend to assume with a federated system like Matrix.

As the operator of a small homeserver, it puts me in a position of having to instruct my users not to use features X, Y and Z of the go-to Matrix client lest they have their communications routed over third parties. Which is all the more irritating when neither I nor my users particularly cared about those features in the first place.

Having the client ask the homeserver as per @MazeChaZer's suggestion seems like a reasonable solution.

@xuebaxuebaxueba
Copy link

Related: #6430, #6802

@MyNameIsJulian MyNameIsJulian changed the title Remove centralization (Jitsi) (deleted) Sep 25, 2019
@Ezwen
Copy link

Ezwen commented Sep 25, 2019

I'm curious, why is this closed? I thought removing Jitsi was part of the plan but not implemented yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants