aboutsummaryrefslogtreecommitdiffhomepage
path: root/client/src/app
diff options
context:
space:
mode:
authorRigel Kent <sendmemail@rigelk.eu>2020-01-10 14:21:46 +0100
committerRigel Kent <sendmemail@rigelk.eu>2020-01-10 14:21:46 +0100
commita6f01388c3bab1ac03d6f1a2cd87331bad5127ce (patch)
tree6efadf7975ec923b2679be789894e1a79a36556c /client/src/app
parent000eb0e40d74e914f6691305511c44e89cd8bf07 (diff)
downloadPeerTube-a6f01388c3bab1ac03d6f1a2cd87331bad5127ce.tar.gz
PeerTube-a6f01388c3bab1ac03d6f1a2cd87331bad5127ce.tar.zst
PeerTube-a6f01388c3bab1ac03d6f1a2cd87331bad5127ce.zip
Reword/update PeerTube page about P2P & Privacy
Diffstat (limited to 'client/src/app')
-rw-r--r--client/src/app/+about/about-peertube/about-peertube.component.html32
1 files changed, 20 insertions, 12 deletions
diff --git a/client/src/app/+about/about-peertube/about-peertube.component.html b/client/src/app/+about/about-peertube/about-peertube.component.html
index 53aee5634..26a3d4554 100644
--- a/client/src/app/+about/about-peertube/about-peertube.component.html
+++ b/client/src/app/+about/about-peertube/about-peertube.component.html
@@ -69,8 +69,14 @@
69 <h3 i18n class="section-title">P2P & Privacy</h3> 69 <h3 i18n class="section-title">P2P & Privacy</h3>
70 70
71 <p i18n> 71 <p i18n>
72 PeerTube uses the BitTorrent protocol to share bandwidth between users. 72 PeerTube uses the BitTorrent protocol to share bandwidth between users by default to help lower the load on the server,
73 This implies that your IP address is stored in the instance's BitTorrent tracker as long as you download or watch the video. 73 but ultimately leaves you the choice to switch back to regular streaming exclusively from the server of the video. What
74 follows applies only if you want to keep using the P2P mode of PeerTube.
75 </p>
76
77 <p>
78 The main threat to your privacy induced by BitTorrent lies in your IP address being stored in the instance's BitTorrent
79 tracker as long as you download or watch the video.
74 </p> 80 </p>
75 81
76 <h6 i18n class="p2p-privacy-title">What are the consequences?</h6> 82 <h6 i18n class="p2p-privacy-title">What are the consequences?</h6>
@@ -122,7 +128,7 @@
122 <h6 i18n class="p2p-privacy-title">How does PeerTube compare with YouTube?</h6> 128 <h6 i18n class="p2p-privacy-title">How does PeerTube compare with YouTube?</h6>
123 129
124 <p i18n> 130 <p i18n>
125 The threats to privacy in YouTube are different from PeerTube's. 131 The threats to privacy with YouTube are different from PeerTube's.
126 In YouTube's case, the platform gathers a huge amount of your personal information (not only your IP) to analyze them and track you. 132 In YouTube's case, the platform gathers a huge amount of your personal information (not only your IP) to analyze them and track you.
127 Moreover, YouTube is owned by Google/Alphabet, a company that tracks you across many websites (via AdSense or Google Analytics). 133 Moreover, YouTube is owned by Google/Alphabet, a company that tracks you across many websites (via AdSense or Google Analytics).
128 </p> 134 </p>
@@ -139,19 +145,21 @@
139 <h6 i18n class="p2p-privacy-title">What will be done to mitigate this problem?</h6> 145 <h6 i18n class="p2p-privacy-title">What will be done to mitigate this problem?</h6>
140 146
141 <p i18n> 147 <p i18n>
142 PeerTube is in its early stages, and want to deliver the best countermeasures possible by the time the stable is released. 148 PeerTube wants to deliver the best countermeasures possible, to give you more choice
143 In the meantime, we want to test different ideas related to this issue: 149 and render attacks less likely. Here is what we put in place so far:
144 </p> 150 </p>
145 151
146 <ul> 152 <ul>
147 <li i18n>Set a limit to the number of peers sent by the tracker</li> 153 <li i18n>We set a limit to the number of peers sent by the tracker</li>
148 <li i18n>Set a limit on the request frequency received by the tracker (being tested)</li> 154 <li i18n>We set a limit on the request frequency received by the tracker</li>
149 <li i18n>Ring a bell if there are unusual requests (being tested)</li> 155 <li i18n>Allow instance admins to disable P2P from the administration interface</li>
150 <li i18n>Disable P2P from the administration interface</li> 156 <li i18n>Automatic video redundancy from some instances: one doesn't know if the IP downloaded the video on purpose or if it a server</li>
151 <li i18n>An automatic video redundancy program: we wouldn't know if the IP downloaded the video on purpose or if it was the
152 automatized program
153 </li>
154 </ul> 157 </ul>
158
159 <p i18n>
160 Ultimately, remember you can always disable P2P by toggling it in the video player, or just by disabling
161 WebRTC in your browser.
162 </p>
155 </div> 163 </div>
156 164
157 </div> 165 </div>