From a562f899bdce53ed4c5673a95a08280a238b462d Mon Sep 17 00:00:00 2001 From: Jos Poortvliet Date: Fri, 3 Apr 2020 10:47:59 +0200 Subject: Update README.md Co-Authored-By: Joas Schilling <213943+nickvergessen@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 63501b374..b7dd27e86 100644 --- a/README.md +++ b/README.md @@ -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) -- cgit v1.2.3