<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 24, 2014 at 12:08 AM, Nick Rout <span dir="ltr"><<a href="mailto:nick.rout@gmail.com" target="_blank">nick.rout@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Sep 24, 2014 at 1:12 PM, Michael T. Dean<br>
<<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br>
> On 09/23/2014 02:17 AM, Joseph Fry wrote:<br>
>><br>
>> On Mon, Sep 22, 2014 at 4:23 PM, Gary Buhrmaster wrote:<br>
>><br>
>><br>
>>> On Mon, Sep 22, 2014 at 7:30 PM, Joseph Fry wrote:<br>
>>> ....<br>
>>>><br>
>>>> Ahh... but is ... considered scraping?<br>
>>><br>
>>> "Duck test". We all know scrapping when we see it.<br>
>>> You want to scrape.<br>
>>><br>
>>>> Perhaps, we can hope that NetFlix won't get too controlling... we pay<br>
>>>> for<br>
>>>> the content, not for their interface.<br>
>>><br>
>>> Their interface *is* their content. They are controlling<br>
>>> their content, and how it is shown to you. I am not a<br>
>>> huge fan of their interface (their content), but I accept it<br>
>>> is their choice.<br>
>>><br>
>>>> If we are turned off by the interface<br>
>>>> and have no way to use something different, they may start to lose<br>
>>>> people.<br>
>>><br>
>>> If every MythTV household that had NetFlix deleted their<br>
>>> account, it would likely not be above the NetFlix<br>
>>> subscriber churn noise (although it might impact the<br>
>>> MythTV user base numbers, if one had to choose<br>
>>> between being a MythTV household and a NetFlix<br>
>>> subscriber due to the WAF). While I am sure you are<br>
>>> the center of the universe, I do not believe that Los<br>
>>> Gatos revolves around you. But please feel free to<br>
>>> demonstrate your principals, and to lead the way,<br>
>>> and to delete your NetFlix account until NetFlix does<br>
>>> it your way. It is the only way to show them who is<br>
>>> in charge here!<br>
>><br>
>><br>
>> My, aren't you negative.<br>
>><br>
>> 1. I am not convinced what I am proposing would really be called<br>
>> scraping...<br>
><br>
><br>
> Call it whatever you want, but its name makes absolutely no difference. The<br>
> approach is explicitly prohibited by the ToU. All you have to do is read<br>
> those terms, which you can do at: <a href="https://www.netflix.com/TermsOfUse" target="_blank">https://www.netflix.com/TermsOfUse</a><br>
><br>
> Since you obviously haven't read it, yet, let me quote one part of it:<br>
><br>
> ----<br>
> 6. Netflix Service<br>
> e. You agree to use the Netflix service, including all features and<br>
> functionalities associated therewith, in accordance with all applicable<br>
> laws, rules and regulations, or other restrictions on use of the service or<br>
> content therein. You agree not to archive, download (other than through<br>
> caching necessary for personal use), reproduce, distribute, modify, display,<br>
> perform, publish, license, create derivative works from, offer for sale, or<br>
> use (except as explicitly authorized in these Terms of Use) content and<br>
> information contained on or obtained from or through the Netflix service<br>
> without express written permission from Netflix and its licensors. You also<br>
> agree not to: circumvent, remove, alter, deactivate, degrade or thwart any<br>
> of the content protections in the Netflix service; use any robot, spider,<br>
> scraper or other automated means to access the Netflix service; decompile,<br>
> reverse engineer or disassemble any software or other products or processes<br>
> accessible through the Netflix service; insert any code or product or<br>
> manipulate the content of the Netflix service in any way; or, use any data<br>
> mining, data gathering or extraction method. In addition, you agree not to<br>
> upload, post, e-mail or otherwise send or transmit any material designed to<br>
> interrupt, destroy or limit the functionality of any computer software or<br>
> hardware or telecommunications equipment associated with the Netflix<br>
> service, including any software viruses or any other computer code, files or<br>
> programs.<br>
> ----<br>
><br>
> Notice the explicit mention of "modify" and "create derivative works from"<br>
> and "manipulate the content of the Netflix service in any way".<br>
><br>
> Lawyered! (And I don't mean what I did to you, but what Netflix did to all<br>
> its users.)<br>
><br>
> Mike<br>
<br>
</div></div>I am not sure that designing a web browser that displays the<br>
information within the myth ui exactly counts as "modifying" content<br>
or information. The whole point of a web browser is to separate<br>
content from presentation (or it bloody used to be!). Nor is it IMHO<br>
"creating a derivative work".<br>
<br>
Manipulating - what the hell does that mean?<br>
<br>
Point given above - is it against the ToU to browse netflix's UI with<br>
a text based browser that dumps all the pictorial stuff on the floor?<br>
<br>
So there you are, lawyered (although admittedly not my specialist area).</blockquote><div><br></div><div>Or to take the argument further... what if I used Chrome's extension engine and simply had it rearrange and theme the netflix UI to look like native mythtv... would that be a violation of the TOS... I'd be using an approved browser after all?</div><div><br></div><div>As far as I am aware, there is no precedent that says that a site's TOS can restrict how the HTML is rendered... every browser renders it different anyway; if there were, then you better believe that ad blockers, script blockers, flash blockers, etc. would have been targeted a long time ago.</div><div><br></div><div>Anyway, this is a dumb argument as I doubt anyone will really want to take the time to write a Netflix plugin like I proposed anyway... or if they do write it they will soon tire of maintaining it. I was only trying to propose, what I thought, a good way to take advantage of the new Linux compatilbility to add Netflix support to mythtv.</div></div></div></div>