Add info about what type of connection is used in chat/during call (p2p, STUN, TUN).
Open
Nobody has claimed this yet.
enhancement
feature: signaling 📶
feature: WebRTC 🚡
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- 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.
Is your feature request related to a problem? Please describe.
...
Describe the solution you'd like
It would be nice to show whether current connection is set up over p2p, STUN or TUN.
Describe alternatives you've considered
...
Additional context
E.g. https://0x0.st/oLTc.jpg
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 by locating the chat and call connection-status UI and the existing handling of p2p, STUN, and TUN connections. Determine where the current connection type can be read and where it should be displayed; done means the active connection type is visible during chats and calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100