wireapp / wireapp/wire-server

Media Server

Open
#901 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
2.8k
Forks
334
Avg merge
1d 7h
Merged PRs (30d)
50

Description

My question:
Hi there,

Which approach would you recommend to server side audio and/or video recording? From a security standpoint it seems that making the recording service a visible participant in a conference would be best, however how to capture the non composited participant streams, and do it in a bandwidth efficient manner? Also eating at the 4 video caller quota with a bot would be significant. Is it technically possible to setup a media server with the necessary authorisations in the call path? Apologies if this is obvious, I dont know much about WebRTC.

Cheers for the really groundbreaking project! Really looking forward to build on top of it.

Jun

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source files or tests; begin with the linked Wire documentation and deployment repository, then trace the WebRTC call path and recording authorization model. Done would be a maintainer-confirmed, documented answer covering participant capture, bandwidth, quota, and whether a media server can be authorized in the call path.

Written by the indexing model from the issue text.

Assessment

Domain
audio-video-rtc, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.