- <context context-type="linenumber">25</context>
- </context-group>
- </trans-unit>
- <trans-unit id="9a612748b059ad246935df17ef4ec4e6afb43a2a">
- <source>
- In theory, someone with enough technical skills could create a script that tracks which IP is downloading which video.
- In practice, this is much more difficult because:
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">27</context>
- </context-group>
- </trans-unit>
- <trans-unit id="64f96be62df4a95a0615b6f630ad25d6348a29d3">
- <source>
- An HTTP request has to be sent on each tracker for each video to spy.
- If we want to spy all PeerTube's videos, we have to send as many requests as there are videos (so potentially a lot)
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">33</context>
- </context-group>
- </trans-unit>
- <trans-unit id="dd9a7a4ee66b0ff3fbb43ba8691ffcd042531611">
- <source>
- For each request sent, the tracker returns random peers at a limited number.
- 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 requests sent to know every peers in the swarm
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">38</context>
- </context-group>
- </trans-unit>
- <trans-unit id="694cf53adfc2afe8afabf713ab00fa114d5d2f8e">
- <source>
- Those requests have to be sent regularly to know who starts/stops watching a video. It is easy to detect that kind of behaviour
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">43</context>
- </context-group>
- </trans-unit>
- <trans-unit id="44bbecddbdf2aad1f4bad97cb806560553fb2ab3">
- <source>
- 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 video
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">47</context>
- </context-group>
- </trans-unit>
- <trans-unit id="fec3239a860de66c718e3442df836b692b8568c3">
- <source>
- The IP address is a vague information : usually, it regularly changes and can represent many persons or entities
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">51</context>
- </context-group>
- </trans-unit>
- <trans-unit id="b4c2ef0143270626106b26196d40baf3439aa7b0">
- <source>
- Web peers are not publicly accessible: because we use WebRTC inside the web browser (<x id="START_LINK" ctype="x-a" equiv-text="<a>"/>with the WebTorrent library<x id="CLOSE_LINK" ctype="x-a" equiv-text="</a>"/>), the protocol is different from classic BitTorrent.
- When you are in a web browser, you send a signal containing your IP address to the tracker that will randomly choose other peers to forward the information to.
- See <x id="START_LINK_1" ctype="x-a" equiv-text="<a>"/>this document<x id="CLOSE_LINK" ctype="x-a" equiv-text="</a>"/> for more information
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">55</context>
- </context-group>
- </trans-unit>
- <trans-unit id="50d8e8388f5ceab292850ed828f306c9f2cab389">
- <source>
- The worst-case scenario of an average person spying on their friends is quite unlikely.
- There are much more effective ways to get that kind of information.
- </source>
- <target> </target>
- <context-group name="null">
- <context context-type="linenumber">62</context>