meeting-rs / meeting.rs Goto Github PK

While current implementation provides only a web application running on browsers, it's possible to create an universal application with slint.

To better collaborate and integrate meeting.rs to voce.chat, we would like to see an API documentation and a docker image.
APIs we'd like to see include:

• Initialization. Calling this is equivalent to having a meeting.rs client, which can be used for event listening, such as who initiated audio and video towards me.
• Create a room. The room number must be unique. We will use meeting.rs in the direct message (DM) settings, which can also be considered as a room for two people. Upon successful creation, we have to notify the other party.
• Leave & destroy the room.

When two clients are in a coordination session, any other clients get in during that window time with the same passphrase will be marked as responders, and hence disrupts the normal session.

Therefor, a session should eliminates any other third client from getting in.

For implementation ,see Using the Screen Capture API for more details.

Ref: https://tailwindcss.com/

Sometimes Responder can't recieve remote streams. It's RtcPeerConnection.ontrack() callback is never called.

During screen sharing sessions, the "audio" option selected with get_display_media_with_constraints does not enable audio sharing as expected. Additionally, attempting to request audio separately using get_user_media_with_constraints also fails to work. This bug report aims to address and resolve these issues to ensure smooth and seamless audio and screen sharing experiences.