-http://www.cbc.ca/aboutcbc/discover/termsofuse.html#ownershi...
-http://www.cbc.ca/aboutcbc/discover/termsofuse.html#ownershi...
From a legal standpoint, how is that any different at all? Would you say that my ISP was also exploiting CBC's content at the time?
Despite some providers' (including CBC's) fanciful claims to the contrary, I don't think or recall any court decision giving control over incoming links to parties being linked to. (Compare to decisions, however controversial, regarding outgoing links, .torrent links being the classic case.)
Now the product is just a web browser whose home page provides hyperlinks to the CBC website, just like my ISP did back in the day. When you buy the app, you are buying the web browser, not the CBC content. The CBC content is only accessible via hyperlinks which you, the user, have to specifically activate.
I get where you are coming from, but it is not clear where the line is drawn. If I create a web browser with a built-in search field that forwards the browser to Google, like many browsers do these days, am I liable to Google in the same way? What if I create an HTML form with a search field that points towards Google? What if I move the HTML form URL into an <a> tag?
HTML/etc is specifically designed to be device and program independent. At every turn developers are cautioned that users may receive only part of the content, that it may not render as expected, etc. There's even a mechanism for checking which client program is being used if you care. As they claim to...
If some downloading of the file is prohibited, they - not the users, should be in trouble. They know of the issue and aren't taking even the most basic of security steps. They're clearly all incompetent, from tech to manager to lawyer - all literally incapable of doing their jobs.
As a Canadian I want their wages refunded. And an apology to the app writer. We pay for CBC either way, the more people who hear it the more worthwhile those tax dollars are.
Hulu already blocked things like boxee based in their custom browser. A better solution for CBC would be I just block to app's access by the user agent.
(I'm not saying you are wrong - just taking it to the extreme)
[I am not the OP, just creating a scenario]
To listen to the content they are streaming on their website, you need to make a copy of it. Now, you could argue that, by creating a URL which will stream that content to any program that asks for it, they have implicitly given everyone permission to copy it in order to listen to it, but I'm not sure that's legally sound, particularly given that AFAICS, the only way in which they publish that URL is in the context of the specific player on their website.
(Now, as a publicly-owned broadcaster, the CBC should be streaming its content in a way that allows anyone - or anyone in Canada, anyway - to access it how they choose; but that's a somewhat separate question.)