]> git.immae.eu Git - github/Chocobozzz/PeerTube.git/blob - client/src/app/+about/about-peertube/about-peertube.component.html
Merge branch 'release/3.3.0' into develop
[github/Chocobozzz/PeerTube.git] / client / src / app / +about / about-peertube / about-peertube.component.html
1 <div class="root">
2 <h1 i18n class="about-peertube-title">
3 What is PeerTube?
4 </h1>
5
6 <img class="mascot" width="121px" height="147px" src="/client/assets/images/mascot/default.svg" alt="mascot"/>
7
8 <div class="description">
9 <p i18n>
10 PeerTube is a self-hosted ActivityPub-federated video streaming platform using P2P directly in your web browser.
11 </p>
12
13 <p i18n>
14 It is free and open-source software, under <a href="https://github.com/Chocobozzz/PeerTube/blob/develop/LICENSE">AGPLv3
15 licence</a>.
16 </p>
17
18 <p i18n>
19 For more information, please visit <a target="_blank" rel="noopener noreferrer" href="https://joinpeertube.org">joinpeertube.org</a>.
20 </p>
21 </div>
22
23 <div class="documentation">
24
25 <div class="card">
26 <div class="card-body">
27 <div class="card-title">
28 <a i18n target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use-setup-account">Use PeerTube
29 documentation</a>
30 </div>
31
32 <div i18n class="card-text">
33 Discover how to setup your account, what is a channel, how to create a playlist and more!
34 </div>
35 </div>
36 </div>
37
38 <div class="card">
39 <div class="card-body">
40 <div class="card-title">
41 <a i18n target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use-third-party-application">PeerTube
42 Applications</a>
43 </div>
44
45 <div i18n class="card-text">
46 Discover unofficial Android applications or browser addons!
47 </div>
48 </div>
49 </div>
50
51 <div class="card">
52 <div class="card-body">
53 <div class="card-title">
54 <a i18n target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/contribute-getting-started">Contribute on
55 PeerTube</a>
56 </div>
57
58 <div i18n class="card-text">
59 Want to help to improve PeerTube? You can translate the web interface, give your feedback or directly contribute to the code!
60 </div>
61 </div>
62 </div>
63 </div>
64
65 <div class="privacy-contributors">
66 <my-about-peertube-contributors></my-about-peertube-contributors>
67
68 <div class="p2p-privacy">
69 <h2 class="section-title">
70 <div class="anchor" id="privacy"></div> <!-- privacy anchor -->
71 <ng-container i18n>P2P & Privacy</ng-container>
72 </h2>
73
74 <p i18n>
75 PeerTube uses the BitTorrent protocol to share bandwidth between users by default to help lower the load on the server,
76 but ultimately leaves you the choice to switch back to regular streaming exclusively from the server of the video. What
77 follows applies only if you want to keep using the P2P mode of PeerTube.
78 </p>
79
80 <p i18n>
81 The main threat to your privacy induced by BitTorrent lies in your IP address being stored in the instance's BitTorrent
82 tracker as long as you download or watch the video.
83 </p>
84
85 <h3 i18n class="p2p-privacy-title">What are the consequences?</h3>
86
87 <p i18n>
88 In theory, someone with enough technical skills could create a script that tracks which IP is downloading which video.
89 In practice, this is much more difficult because:
90 </p>
91
92 <ul>
93 <li i18n>
94 An HTTP request has to be sent on each tracker for each video to spy.
95 If we want to spy all PeerTube's videos, we have to send as many requests as there are videos (so potentially a lot)
96 </li>
97
98 <li i18n>
99 For each request sent, the tracker returns random peers at a limited number.
100 For instance, if there are 1000 peers in the swarm and the tracker sends only 20 peers for each request, there must be at least 50
101 requests sent to know every peer in the swarm
102 </li>
103
104 <li i18n>
105 Those requests have to be sent regularly to know who starts/stops watching a video. It is easy to detect that kind of behaviour
106 </li>
107
108 <li i18n>
109 If an IP address is stored in the tracker, it doesn't mean that the person behind the IP (if this person exists) has watched the
110 video
111 </li>
112
113 <li i18n>
114 The IP address is a vague information: usually, it regularly changes and can represent many persons or entities
115 </li>
116
117 <li i18n>
118 Web peers are not publicly accessible: because we use the websocket transport, the protocol is different from classic BitTorrent tracker.
119 When you are in a web browser, you send a signal containing your IP address to the tracker that will randomly choose other peers
120 to forward the information to.
121 See <a href="https://github.com/yciabaud/webtorrent/blob/beps/bep_webrtc.rst">this document</a> for more information
122 </li>
123 </ul>
124
125 <p i18n>
126 The worst-case scenario of an average person spying on their friends is quite unlikely.
127 There are much more effective ways to get that kind of information.
128 </p>
129
130 <h3 i18n class="p2p-privacy-title">How does PeerTube compare with YouTube?</h3>
131
132 <p i18n>
133 The threats to privacy with YouTube are different from PeerTube's.
134 In YouTube's case, the platform gathers a huge amount of your personal information (not only your IP) to analyze them and track you.
135 Moreover, YouTube is owned by Google/Alphabet, a company that tracks you across many websites (via AdSense or Google Analytics).
136 </p>
137
138 <h3 i18n class="p2p-privacy-title">What can I do to limit the exposure of my IP address?</h3>
139
140 <p i18n>
141 Your IP address is public so every time you consult a website, there is a number of actors (in addition to the final website) seeing
142 your IP in their connection logs: ISP/routers/trackers/CDN and more.
143 PeerTube is transparent about it: we warn you that if you want to keep your IP private, you must use a VPN or Tor Browser.
144 Thinking that removing P2P from PeerTube will give you back anonymity doesn't make sense.
145 </p>
146
147 <h3 i18n class="p2p-privacy-title">What will be done to mitigate this problem?</h3>
148
149 <p i18n>
150 PeerTube wants to deliver the best countermeasures possible, to give you more choice
151 and render attacks less likely. Here is what we put in place so far:
152 </p>
153
154 <ul>
155 <li i18n>We set a limit to the number of peers sent by the tracker</li>
156 <li i18n>We set a limit on the request frequency received by the tracker</li>
157 <li i18n>Allow instance admins to disable P2P from the administration interface</li>
158 </ul>
159
160 <p i18n>
161 Ultimately, remember you can always disable P2P by toggling it in the video player, or just by disabling
162 WebRTC in your browser.
163 </p>
164 </div>
165
166 </div>
167 </div>