diff options
author | Mark Van den Borre <mark+github@markvdb.be> | 2020-10-21 23:07:19 +0200 |
---|---|---|
committer | Chocobozzz <chocobozzz@cpy.re> | 2020-10-23 15:39:52 +0200 |
commit | d4301a6c8be7231860eee48df25d82c093a3b43c (patch) | |
tree | 35e51955da161acececd942b3dab45e40bced6e6 | |
parent | 313921b50fda6bfd2942e45e3c9a0547ff01880b (diff) | |
download | PeerTube-d4301a6c8be7231860eee48df25d82c093a3b43c.tar.gz PeerTube-d4301a6c8be7231860eee48df25d82c093a3b43c.tar.zst PeerTube-d4301a6c8be7231860eee48df25d82c093a3b43c.zip |
s/franglais/English/
Suggesting some minor language improvements after a quick skim. s/franglais/English mostly ("My flowers are beautiful!").
Thank you for your work on PeerTube. Much appreciated. Looking forward to the live streaming features!
-rw-r--r-- | FAQ.md | 16 |
1 files changed, 7 insertions, 9 deletions
@@ -71,15 +71,13 @@ with a `Content-Range` HTTP header. | |||
71 | 71 | ||
72 | ## If a client requests each chunk of a video through HTTP, will the server be overloaded? | 72 | ## If a client requests each chunk of a video through HTTP, will the server be overloaded? |
73 | 73 | ||
74 | Not really. Reverse proxies like Nginx handle very well requests of static | 74 | Not really. Reverse proxies like Nginx handle static file requests very well. In my tests, it can send chunks at 10MB/s without consuming more than 5% CPU on a very small VPS. |
75 | files. In my tests, it can send chunks at 10MB/s without consuming more than 5% | ||
76 | of CPU on a very small VPS. | ||
77 | 75 | ||
78 | 76 | ||
79 | ## Will an index of all the videos of servers you follow be too large for small servers? | 77 | ## Will an index of all the videos of servers you follow be too large for small servers? |
80 | 78 | ||
81 | In our benchmarks, 1,000,000 videos takes around 2GB of storage on PostgreSQL. | 79 | In our benchmarks, 1,000,000 videos consume around 2GB of PostgreSQL storage. |
82 | We think it is acceptable for a video platform. | 80 | We think that is acceptable for a video platform. |
83 | 81 | ||
84 | 82 | ||
85 | ## Which container formats can I use for the videos I want to upload? | 83 | ## Which container formats can I use for the videos I want to upload? |
@@ -94,13 +92,13 @@ and FLV formats when transcoding is enabled on their instance. | |||
94 | It's not officially supported, but you can try the `update-host` script: https://docs.joinpeertube.org/#/maintain-tools?id=update-hostjs | 92 | It's not officially supported, but you can try the `update-host` script: https://docs.joinpeertube.org/#/maintain-tools?id=update-hostjs |
95 | 93 | ||
96 | 94 | ||
97 | ## Why do we have to put our Twitter username in PeerTube configuration? | 95 | ## Why do we have to put our Twitter username in the PeerTube configuration? |
98 | 96 | ||
99 | You don't have to: we set a default value if you don't have a Twitter account. | 97 | You don't have to: we set a default value if you don't have a Twitter account. |
100 | We need this information because Twitter requires an account for links share/videos embed on their platform. | 98 | We need this information because Twitter requires an account for links share/videos embed on their platform. |
101 | 99 | ||
102 | 100 | ||
103 | ## How video views are calculated? | 101 | ## How are video views counted? |
104 | 102 | ||
105 | Your web browser sends a view to the server after 30 seconds of playback. If a video is less than 30 seconds in length, a view is sent after 75% of the video. After giving a view, that IP address cannot add another view in the next hour. | 103 | Your web browser sends a view to the server after 30 seconds of playback. If a video is less than 30 seconds in length, a view is sent after 75% of the video. After giving a view, that IP address cannot add another view in the next hour. |
106 | Views are buffered, so don't panic if the view counter stays the same after you watched a video. | 104 | Views are buffered, so don't panic if the view counter stays the same after you watched a video. |
@@ -122,12 +120,12 @@ So you would need: | |||
122 | 120 | ||
123 | Yes you can, but you won't be able to send data to users that watch the video in their web browser. | 121 | Yes you can, but you won't be able to send data to users that watch the video in their web browser. |
124 | The reason is they connect to peers through WebRTC whereas your BitTorrent client uses classic TCP/UDP. | 122 | The reason is they connect to peers through WebRTC whereas your BitTorrent client uses classic TCP/UDP. |
125 | To check if your BitTorrent client supports WebTorrent you can see this issue: https://github.com/webtorrent/webtorrent/issues/369 | 123 | You can check if your BitTorrent client supports WebTorrent in this issue: https://github.com/webtorrent/webtorrent/issues/369 |
126 | 124 | ||
127 | 125 | ||
128 | ## Why host on GitHub and Framagit? | 126 | ## Why host on GitHub and Framagit? |
129 | 127 | ||
130 | The project has initially been hosted on GitHub by Chocobozzz. A full migration to [Framagit](https://framagit.org/framasoft/peertube/PeerTube) would be ideal now that Framasoft supports PeerTube, but it would take a lot of time and is an ongoing effort. | 128 | The project was initially hosted on GitHub by Chocobozzz. A full migration to [Framagit](https://framagit.org/framasoft/peertube/PeerTube) would be ideal now that Framasoft supports PeerTube, but it would take a lot of time and is an ongoing effort. |
131 | 129 | ||
132 | 130 | ||
133 | ## Are you going to use the Steem blockchain? | 131 | ## Are you going to use the Steem blockchain? |