-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Rooms as VoIP/Rooms as Video #730
Comments
So I was thinking about this and how video/voice rooms might be function, given the decentralized & open nature of matrix. I talked a bit about this in my summary here, but the key thing here is that voice rooms should be abstract representations of capability, and should support multiple backends to drive the experience. Remember, atm some people use jitsi for calls, some people use mumble, etc. The voice room should just provide a common interface for all of this, but still allow all these different backends, which likely means that it's gonna be up to the server to support different voice backends. I'd totally willing to lend a hand to draft out an MSC for this, but I'm personally unfamiliar with how matrix approaches API design, so I'm not sure how much I could do by myself. |
It would be awesome! |
A key feature that need to be implemented |
like this : matrix-org/matrix-spec-proposals#3401 ? |
Is your feature request related to a problem? Please describe.
A friend complained about a lack of a Discord-like persistent voice channel. Perhaps persistent video rooms could also be implemented.
Describe the solution you'd like
Maybe a room type such as
m.room.voice
orm.room.video
would work? I'm not too familiar with the matrix doc so I'm not sure if this is possible with current Matrix technology.With the upcoming Matrix Spaces (MSC1772), persistent voice rooms and persistent video rooms could add a lot to the experience.
The text was updated successfully, but these errors were encountered: