+It is a BitTorrent extension that allows a server to seed a file through HTTP.
+It just needs to statically serve a file, then the clients will request chunks
+with a `Content-Range` HTTP header.
+
+
+## If a client requests each chunk of a video through HTTP, will the server be overloaded?
+
+Not really. Reverse proxies like Nginx handle very well requests of static
+files. In my tests, it can send chunks at 10MB/s without consuming more than 5%
+of CPU on a very small VPS.
+
+
+## Will an index of all the videos of servers you follow be too large for small servers?
+
+In our benchmarks, 1,000,000 videos takes around 2GB of storage on PostgreSQL.
+We think it is acceptable for a video platform.
+
+
+## Which container formats can I use for the videos I want to upload?
+
+WEBM, MP4 or OGV videos are supported by default (they are streamable formats),
+but instance administrators can additionally enable support for MKV, MOV, AVI
+and FLV formats when transcoding is enabled on their instance.
+
+
+## I want to change my domain name, how can I do that?
+
+It's not officially supported, but you can try the `update-host` script: https://docs.joinpeertube.org/#/maintain-tools?id=update-hostjs
+
+
+## Why do we have to put our Twitter username in PeerTube configuration?
+
+You don't have to: we set a default value if you don't have a Twitter account.
+We need this information because Twitter requires an account for links share/videos embed on their platform.
+
+
+## How video views are calculated?
+
+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.
+Views are buffered, so don't panic if the view counter stays the same after you watched a video.
+
+
+## Should I have a big server to run PeerTube?
+
+Not really. For instance, the demonstration server [https://peertube.cpy.re](https://peertube.cpy.re) has 2 vCore and 2GB of RAM and consumes on average:
+ * **CPU** -> nginx ~ 20%, peertube ~ 10%, postgres ~ 1%, redis ~ 3%
+ * **RAM** -> nginx ~ 6MB, peertube ~ 120MB, postgres ~ 10MB, redis ~ 5MB
+
+So you would need:
+ * **CPU** 1 core if you don't enable transcoding, 2 at least if you enable it (works with 1 but this is really slow)
+ * **RAM** 1GB
+ * **Storage** Completely depends on how many videos your users will upload
+
+
+## Can I seed videos with my classic BitTorrent client (Transmission, rTorrent...)?
+
+Yes you can, but you won't be able to send data to users that watch the video in their web browser.
+The reason is they connect to peers through WebRTC whereas your BitTorrent client uses classic TCP/UDP.
+To check if your BitTorrent client supports WebTorrent you can see this issue: https://github.com/webtorrent/webtorrent/issues/369
+
+
+## Why host on GitHub and Framagit?
+
+The project has initially been hosted on GitHub by Chocobozzz. A full migration to [Framagit](https://framagit.org/chocobozzz/PeerTube) would be ideal now that Framasoft supports PeerTube, but it would take a lot of time and is an ongoing effort.
+
+
+## Are you going to use the Steem blockchain?
+
+Short answer: no, since like most appchains/votechains, it modifies the dynamic of creation, and as such cannot be integrated into mainline PeerTube. Read more about that in [the dedicated section](#what-is-creation-dynamic-and-why-not-modify-it).