<div dir="ltr">Yesterday I forwarded this thread to Neil Hunt - the Chief Product Officer at Netflix with the hope that he would read it and have received the following reply a few hours ago.<div><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote"><span style="font-size:12.8px">Noted - this will go to the right technical people.</span><br></blockquote><div class="gmail_extra"><br></div><div class="gmail_extra">I'm hoping this is a sign Netflix will take this seriously.</div><div class="gmail_extra"><br></div><div class="gmail_extra">-- Jonas</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 27, 2016 at 12:20 PM,  <span dir="ltr"><<a href="mailto:tor_manager@autistici.org" target="_blank">tor_manager@autistici.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi everyone,<br>
apparently this is happening with a lot of relays node (My italian relay node was blocked too) <a href="https://www.reddit.com/r/netflix/comments/472kqu/netflix_started_blocking_tor_relayonly_nodes/" rel="noreferrer" target="_blank">https://www.reddit.com/r/netflix/comments/472kqu/netflix_started_blocking_tor_relayonly_nodes/</a><br>
As Roger said we have to try to identify someone inside Netflix to pitch "our cause", on the other hand, it will probably be really useful to try to step up also in public (social/PR), for example asking to EFF to support this.<br>
<br>
We are struggling convincing people to open nodes, we really have to protect them, we will see a decrease number of nodes<br>
<br>
Aidoru<div><div><br>
<br>
On 2016-02-26 23:58, Roger Dingledine wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On Sat, Feb 27, 2016 at 12:42:38AM +0100, Gero Kuehn wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
¬†They did however not<br>
leave the impression that they a) care or b) intend to fix this at some<br>
point by parsing the Tor network information properly instead of using<br>
whatever cheap&wrong hack they use now.<br>
</blockquote>
<br>
There is actually a service that they can use to do this parsing<br>
for them:<br>
<a href="https://check.torproject.org/cgi-bin/TorBulkExitList.py" rel="noreferrer" target="_blank">https://check.torproject.org/cgi-bin/TorBulkExitList.py</a><br>
e.g.<br>
<a href="https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=128.31.0.34&port=443" rel="noreferrer" target="_blank">https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=128.31.0.34&port=443</a><br>
<br>
Now, I bet Netflix has more than one IP address. It would not be hard<br>
to adapt this service to help them do what they should be wanting to do.<br>
<br>
See <a href="https://www.torproject.org/docs/faq-abuse#Bans" rel="noreferrer" target="_blank">https://www.torproject.org/docs/faq-abuse#Bans</a> for more details.<br>
<br>
One of our next steps might be to find a useful technical contact<br>
inside Netflix, so they can start doing this advocacy and education from<br>
the inside.<br>
<br>
--Roger<br>
</blockquote>
<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</div></div></blockquote></div><br></div></div>