diff options
| -rw-r--r-- | README.md | 2 | ||||
| -rw-r--r-- | appinfo/info.xml | 1 | ||||
| -rw-r--r-- | docs/call-in-action.png | bin | 1494800 -> 1016791 bytes | |||
| -rw-r--r-- | docs/file-darg-and-drop.png | bin | 0 -> 141838 bytes |
4 files changed, 2 insertions, 1 deletions
@@ -45,7 +45,7 @@ A single video stream currently uses about 1 Mbit/sec and the total required ban 1 Mbit/s * (participants - 1) ``` - + This means that in a call with 5 participants, each has to send and receive about 4 Mbit/sec. Given the asymetric nature of most typical broadband connections, it's sending video that quickly becomes the bottleneck. Moreover, decoding all those video streams puts a big strain on the system of each participant. diff --git a/appinfo/info.xml b/appinfo/info.xml index b95721982..f52424540 100644 --- a/appinfo/info.xml +++ b/appinfo/info.xml @@ -42,6 +42,7 @@ And in the works for the [coming versions](https://github.com/nextcloud/spreed/m <screenshot>https://raw.githubusercontent.com/nextcloud/spreed/master/docs/call-in-action.png</screenshot> <screenshot>https://raw.githubusercontent.com/nextcloud/spreed/master/docs/chat.png</screenshot> + <screenshot>https://raw.githubusercontent.com/nextcloud/spreed/master/docs/file-darg-and-drop.png</screenshot> <screenshot>https://raw.githubusercontent.com/nextcloud/spreed/master/docs/screensharing.png</screenshot> <screenshot>https://raw.githubusercontent.com/nextcloud/spreed/master/docs/video-verfication.png</screenshot> diff --git a/docs/call-in-action.png b/docs/call-in-action.png Binary files differindex edad49288..0ae15f3a7 100644 --- a/docs/call-in-action.png +++ b/docs/call-in-action.png diff --git a/docs/file-darg-and-drop.png b/docs/file-darg-and-drop.png Binary files differnew file mode 100644 index 000000000..9d1762568 --- /dev/null +++ b/docs/file-darg-and-drop.png |
