nextcloud / nextcloud/talk-android
Refresh capabilities and signaling settings on `X-Nextcloud-Talk-Hash` header change
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Priority raises with #851
The requests for:
/ocs/v2.php/apps/spreed/api/v1/room/ocs/v2.php/apps/spreed/api/v2/room/ocs/v2.php/apps/spreed/api/v1/room/{token}/ocs/v2.php/apps/spreed/api/v2/room/{token}
have a new X-Nextcloud-Talk-Hash header which contains a sha1 over some of the most important talk configs that affect communication and connections.
When you receive a different value on subsequent requests, the capabilities and the signaling settings should be refreshed asap.
See https://github.com/nextcloud/spreed/pull/3662/commits/44131a87074a2a9de02dffac5383cac8548cc88a for doc changes
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
Locate the Android handling for the listed room API requests and inspect how the X-Nextcloud-Talk-Hash header is currently processed. Compare the referenced spreed documentation changes, then verify that a changed header refreshes capabilities and signaling settings as soon as possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- audio-video-rtc, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100