aboutsummaryrefslogtreecommitdiffhomepage
path: root/FAQ.md
diff options
context:
space:
mode:
Diffstat (limited to 'FAQ.md')
-rw-r--r--FAQ.md52
1 files changed, 51 insertions, 1 deletions
diff --git a/FAQ.md b/FAQ.md
index ab565c59d..fb3969a04 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -1,5 +1,23 @@
1# FAQ 1# FAQ
2 2
3<!-- Table of contents generated with DocToc: https://github.com/thlorenz/doctoc -->
4<!-- START doctoc generated TOC please keep comment here to allow auto update -->
5<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
6
7
8- [If nobody watches a video, is it seeded?](#if-nobody-watches-a-video-is-it-seeded)
9- [What is WebSeed?](#what-is-webseed)
10- [If a client requests each chunk of a video through HTTP, will the server be overloaded?](#if-a-client-requests-each-chunk-of-a-video-through-http-will-the-server-be-overloaded)
11- [Will an index of all the videos of servers you follow be too large for small servers?](#will-an-index-of-all-the-videos-of-servers-you-follow-be-too-large-for-small-servers)
12- [What codecs can I use for the videos I want to upload?](#what-codecs-can-i-use-for-the-videos-i-want-to-upload)
13- [I want to change my host, how can I do that?](#i-want-to-change-my-host-how-can-i-do-that)
14- [Should I have a big server to run PeerTube?](#should-i-have-a-big-server-to-run-peertube)
15- [Are you going to use the Steem blockchain?](#are-you-going-to-use-the-steem-blockchain)
16- [Are you going to support advertisements?](#are-you-going-to-support-advertisements)
17- [What is "creation dynamic" and why not modify it?](#what-is-creation-dynamic-and-why-not-modify-it)
18
19<!-- END doctoc generated TOC please keep comment here to allow auto update -->
20
3## If nobody watches a video, is it seeded? 21## If nobody watches a video, is it seeded?
4 22
5Yes, the origin server always seeds videos uploaded on it thanks to 23Yes, the origin server always seeds videos uploaded on it thanks to
@@ -44,9 +62,41 @@ If you don't have any followers, update your configuration and run
44Not 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: 62Not 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:
45 * **CPU** -> nginx ~ 20%, peertube ~ 10%, postgres ~ 1%, redis ~ 3% 63 * **CPU** -> nginx ~ 20%, peertube ~ 10%, postgres ~ 1%, redis ~ 3%
46 * **RAM** -> nginx ~ 6MB, peertube ~ 120MB, postgres ~ 10MB, redis ~ 5MB 64 * **RAM** -> nginx ~ 6MB, peertube ~ 120MB, postgres ~ 10MB, redis ~ 5MB
47 65
48So you would need: 66So you would need:
49 * **CPU** 1 core if you don't enable transcoding, 2 at least if you enable it 67 * **CPU** 1 core if you don't enable transcoding, 2 at least if you enable it
50 * **RAM** 1GB 68 * **RAM** 1GB
51 * **Storage** Completely depends on how many videos your users will upload 69 * **Storage** Completely depends on how many videos your users will upload
52 70
71
72## Are you going to use the Steem blockchain?
73
74Short 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).
75
76Long answer is that the Steem blockchain goes astray of its promises of fairness and decentralization: the deliberate relaunching of the currency to ensure centralization, and the stake-based voting power, makes manipulation by wealthy users inevitable ([source here](https://decentralize.today/the-ugly-truth-behind-steemit-1a525f5e156)).
77Worse, money generated primarily goes to stakeholders ([source here](https://steemit.com/steemit/@orly/how-the-steem-pyramid-scheme-really-works) ).
78For more information, read the complete whitepaper analysis done by [Tone Vays](https://twitter.com/ToneVays/status/761975587451928576).
79
80## Are you going to support advertisements?
81
82Short answer: no, we don't want advertisers to dictate which content should be financed.
83That would modify the dynamic of creation; as such it cannot be integrated into mainline PeerTube.
84Read more about that in [the dedicated section](#what-is-creation-dynamic-and-why-not-modify-it).
85
86The long answer is probably more subtle. YouTube has shaped generations of video creators by making it easy to place ads;
87but making big money with the platform can be a challenge.
88A typical video ad runs between $.10 and $.30 per 1000 views (as of March 2018).
89More than 70% of video creators use ads as the main way to make money on YouTube, yet less than 3% of video creators make a living out of their YouTube activity (with partnerships and commissions, otherwise counting only ad revenue it drops to 1%).
90Read more about it in the 2018 study by Mathias Bärtl, [*YouTube channels, uploads and views: A statistical analysis of the past 10 years*](https://www.dropbox.com/s/0cq4wtxm83s95t2/10.1177%401354856517736979.pdf?dl=0).
91To the best of our knowledge, small and medium-community creators are better off getting support from their community on platforms such as Liberapay, Tipeee or Patreon.
92Moreover, don't forget that advertisers already pay considering YouTube's large user base; with PeerTube's way smaller user base and refusal of user profiling, a pay-per-view that's lower than YouTube's could only be expected.
93
94## What is "creation dynamic" and why not modify it?
95
96We define creation dynamic as the way any original content, regardless of its monetary value, is created and incentivized.
97We want to limit as much as possible the influence our platform could have on authors in order to stay neutral. We are not curators, and want to limit the scope of PeerTube instance owners and administrators' responsibilities to moderation tasks only.
98
99If you still want to use a functionality potentially altering that state of things, then you could interface with our upcoming plug-in system, which will be the place to integrate such features in the near future.
100
101With that being said, know that we are not against these features *per se*.
102We are always open to discussion about potential PRs bringing in features, even of that kind. But we certainly won't dedicate our limited resources to develop them ourselves when there is so much to be done elsewhere.