diff options
| author | Jos Poortvliet <jospoortvliet@gmail.com> | 2020-04-03 10:47:59 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-03 10:47:59 +0200 |
| commit | a562f899bdce53ed4c5673a95a08280a238b462d (patch) | |
| tree | 99462603628071d4c46faa48acf07c9eca1ef590 /README.md | |
| parent | a0d928381ddb5329d52aadc2f14fcae39209ad3f (diff) | |
Update README.md
Co-Authored-By: Joas Schilling <213943+nickvergessen@users.noreply.github.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -39,7 +39,7 @@ Here's a short [video](https://youtu.be/KdTsWIy4eN0) on how it's done. Talk works peer to peer, that is, each participant sends an end-to-end encrypted stream to each other participant and receives one stream per other participant. This grows bandwidth usage with the number of participants. As most users are on an asymetric local internet connection, the sending bandwidth often becomes the bottleneck. A typical Nextcloud Talk instance can handle a few dozen calls, but each call can have only 4-6 participants with video depending on the participants' bandwidth. Without video, more is possible. -A single video stream currently uses about 1 mb/sec and the total required bandwidth can be calculated as follows: +A single video stream currently uses about 1 mbit/sec and the total required bandwidth can be calculated as follows: ``` 1 mb/s * (participants - 1) |