Support for internal signaling federation
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 350
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
From #12604
Joining/leaving with the federated session IDs seems to work with internal signaling too (and the participant status is eventually updated in the sidebar), but is something else needed? For example, relaying the ping from the federated server to the host or something like that.
It should be verified if cleaning participants works as intended (it seems that only secondary sessions are cleaned when inactive, but if a single session is kept in the room without a ping it is not cleaned), as it could be relevant for internal signaling if the behaviour is changed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the participant-cleaning logic in lib/Controller/RoomController.php around lines 944-952 and review related pull request #12741. Verify internal signaling for federated session joins, leaves, pings, and inactive participant cleanup; done means the required behavior is established and covered by the relevant checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- audio-video-rtc, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100