"I cant find the edit button and I swear I spaced that stuff out. I don't know why its a giant wall of text :("
Your comment might have been set to HTML instead of Plain Text? Plain Text automatically spaces lines when you do, with HTML you have to make the spacing explicit in HTML.
Re: There is zero NEED for cell phones in school class rooms.
"There is zero NEED for cell phones in school class rooms. You are there to pay attention to the teacher; not texting or making phone calls. After all passing notes in classes is a no-no too."
What Ron said. Plus, this really has less to do with "cell phones" and more to do with mobile, handheld computers (even though McGuinty still calls them cell phones).
Re: Re: Re: Re: Re: Re: Re: the GPL is dead, it just does not know it yet
Bradley Kuhn isn't speaking on behalf of the FSF in that post, but I think he's opinion is shared by folks at the FSF (and he has been a volunteer, Executive Director, and now he's on the board).
Of course, but my point is that if the software is public domain, I don't have to release the source code at all, like I would if it were GPL.
Yes, but the FSF still considers public domain software and non-copyleft (e.g. MIT, BSD, or Apache licensed) software to be free software, even though there's no legal requirement for people to release the source code. The source code must be available for software to be consider free, but it doesn't have to be a requirement of the license for the software to be considered free.
"Where I'm really waiting for someone to demonstrate I'm wrong is to show how enforcement of the GPL and similar licenses doesn't depend at all for any of its strength upon copyright law."
You're not going to be proven wrong there, because all of the strength of the GPL does come from copyright. But what I'm arguing, and what Bradley Kuhn explains, is that GPL enforcement is only a tactic, not a goal. That is, having a way to reverse copyright and create requirements for freedom is a clever hack on a broken system. But, there are other ways to make the source code available. Kuhn suggests that source be registered with a copyright registration, and then released to the public when copyright expires (assuming a reasonable time frame were adopted).
But, there are also social tools and practices that can be used to make source code available. We can already see how that's done with permissive non-copyleft licenses. Often, the reasons to contribute source code are social or practical. Apple and Google both contribute to WebKit, because they want it to be strong for Safari and Chromium.
Now, clearly, there are problems still from a free software perspective, as both companies bundle up that free code into proprietary browsers. But you can see how a more reasonable copyright law could solve some of the problems. Apple's model would still present a challenge, whereas Safari is a proprietary browser built on an free software rendering enginer. But Chromium, which is free software, gets packaged up by Google as Chrome, which is not free software. But the code is essentially the same, minus the branding and the license. With a more reasonable copyright law, Chrome's license becomes even less of an issue from the perspective of free software.
I'm not saying that I know how the challenge would be overcome... but there are ways to create positive incentives for companies to share source code, even companies that are extremely proprietary like Apple, or companies that want to built proprietary products off the free base, like Google. The GPL takes advantage of copyright to create a strong legal incentive, but there could be other innovative ways to create incentives without depending on copyright.
Another social way might be with consumer pressure (though, it's a bit of a pipe dream now). For example, I don't think many people would buy a screwdriver from Home Depot if it came with a ridiculous EULA, could only be used with Home Depot screws, and you weren't allowed to switch the bits yourself... people just wouldn't be stupid enough to give away their freedom to use their own tools like that. Generally, they'd buy a screw driver they could own. The FSF tries to explain the value of software freedom in that sense too. For a business, there are practical benefits to controlling your own tools, to have a selection of vendors that can provide support or a wide range of developers you could hire to improve the software. For an individual, there can be benefits to "owning" (i.e. being in control) of software rather than just licensing it as well.
I guess what I'm trying to say is that there's a positive re-enforcement approach that's possible too. The GPL gets its power fully from copyright, but there are other ways to encourage people to release source code, and the weakening of the GPL would be a small trade for a more reasonable copyright law.
(Sorry for the length and rambling nature of the comment... hope I'm making sense!)
"First of all there is the legal argument and I am quite surprised that Techdirt didn't call out Matt Mullenweg's general efforts to expand the definition of a derivative work. Many experts have given strong legal arguments that plugins are not derivative works at all. And these certainly are by no means "novel legal arguments." It really is a stretch to legally justify the Software Freedom Law Center's opinion that combining in memory constitutes a new copyrightable work that falls under the legal definition of a derivative work. You certainly cannot distribute the memory contents to another person and this combining has been done by the end user. Sure the Thesis theme has some other issues that do make it a possible copyright violation, but that did not even come up until later in the discussion."
Agreed that the interesting legal arguments around the main quesiton -- are themes subject to the GPL? -- were buried. I was trying to keep the post on a level of a decent summary, without getting too deep into the legalities. I could have done a better job of highlighting the legitimate legal opinions that aren't in agreement with the SFLC. Pearson's reliance on those arguments was kind of lame, given that he'd subclassed and copied from the WordPress codebase.
"The separate issue here is one of a moral responsibility to the free software community. The moral responsibility specifically is that if you build upon open and free software you should in turn make your software open and free as well. The problem is that the moral arguments are often used to justify the legal arguments but that just doesn't work and it confuses the whole matter.
Mullenweg really just needs to admit that the legal argument is weak (or is at least highly arguable) and focus on the moral responsibility. It's much harder for someone to argue the moral responsibility end of it, especially when the entire open source community supports it."
I'm not sure what to think of the legal arguments. I think there is a huge amount of grey area. It likely would depend on a specific analysis of the code of any given theme... though, I think it's unlikely that the PHP code in many themes is that separable, or written entirely from scratch (as opposed to derived from another GPLed WordPress theme). But there are lots of legal challenges that could be made around interoperability and fair use.
But, even the SFLC said the GPL wouldn't apply to JavaScript or CSS, which does make a theme fairly useless in many ways, hence the continued WordPress.com policy of only promoting commercial themes that are 100% GPL (which implicitly acknowledge that fact that there's nothing wrong with selling GPL code, even if some in the community don't quite get that—there's nothing unethical about making money off free software, I think the accusations were around profiting from a potential license violation).
I agree that there's a moral, and a pragmatic and social argument to be made for encouraging fully GPL themes and extensions. I support the WordPress.com policy to only endorse GPL code, and other project websites, like drupal.org, do the same. It's better for the health of the ecosystem if extensions to the platform provide the same freedoms of the platform itself, otherwise you can run into lock-in at the plugin/theme level, for example. So, even if the legal argument for themes being subject to the GPL is weak (and at best with the SFLC's opinion, it still only applies to the PHP), there are other reasons to apply social and business pressure to theme (and plugin) developers to go GPL.
Good call. The legal and moral/social arguments could be better separated. I don't think anyone representative of WordPress.com is suggesting that it's bad to make money from themes though, they even list commercial themes as long as they're 100% GPL.
Thanks for sharing that link, hadn't seen that post. The author doesn't really address the extent to which Thesis had copied WordPress code until the comments, but there are a lot of important arguments in the post.
"copyleft is merely a tool that diffuses the proprietary copyright weaponry... But, if it were possible to really consider reduction in copyright control over software, then I don't know of a single GPL proponent who wouldn't want to bilaterally reduce copyright's scope for software."
Copyleft is a jujitsu move. Though jujitsu depends on using the force of your opponent against him, it doesn't mean that you want your opponent to attack you.
Which means if the GPL destroys copyright it destroys itself, and yes, then people will just make it proprietary and ignore the GPL.
I don't get the argument that since the GPL relies on copyright it can't do a good job of undermining overly restrive copyright. It's just a means to an end, while copyright law is out of whack. It's not necessary at all for free software, just often a useful tactic while restrictive copyright is the default.
And the GPL is a hack (I didn't say "hack job"), but so is the Apache license. They both have their strengths and weaknesses, as far as removing the barriers of restrictive copyright go.
And other licenses being more popular than the GPL? Do you have anything to back that up?
Well, first, where does anyone say that "building something that operates in a WordPress environment" is subject to the GPL? You need to be distributing the software before the GPL's source code requirements kick in (i.e. it's not AGPL, so you build whatevdr you want on top of WordPress on your own servers without having to share it). And Automattic does this, they have services like Akismet and Gravatar which, if I recall correctly, are not GPL. Clearly, the belief isn't that anything operating in a WP environment is subject to the GPL, but rather that anything building off the WP codebase -- like a theme or plugin -- is subject to the GPL.
Second, distributing non-GPL themes (I assume that's what you meant) and extensions harm WP in the sense that WP is built on software freedom; it was born from the ability to fork a codebase, and relies on that freedom to develop and grow. Non-free extensions to WP are corrosive to an environment of software freedom, because you start hitting dead ends, or getting non-free dependencies that would thwart the ability for users to practically exercise their freedoms. But, except in cases like that of Chris publicly claiming that WP's license doesn't apply to him (but his license should apply to everyone else), legal action would be a lot more divisive.
The fact that they haven't sued anyone isn't evidence that proprietary themes aren't harmful, it's just evidence that they're using proportional means. Legal action should be a last resort.
I think the claim that they resort to public shaming too quickly is more relevant, because some developers just might not understand the requirements of the GPL. Any examples, outside of Thesis, that you can point to of WordPress being too quick to put public pressure on devs (i.e. before doing so privately)?
"Matt from WordPress and Chris from DIYThemes (Thesis) have been sniping at each other since WordPress took the legally untested stance that all themes should be released GPL 3 years ago."
Legally untested, maybe, but pretty widely agreed upon by legal experts who work with free software licenss. If Chris really thought it was such a flimsy legal argument, what difference would it make that he was subclassing or copying and pasting WordPress code?
And WordPress isn't alone in taking that stance. Everything on drupal.org must be GPL, including modules and themes, for example. And, I think it's a good idea that, even if only the PHP portion of WP themes are likely to technically be required to be GPL, WP only endorses themes that are fully GPL. That way you know you have the freedoms to study, use, modify and redistribute everything from wordpress.org, rather than having to pluck out proprietary parts of a theme from DIYThemes or someone.
Really, if Chris doesn't want to be work with the GPL or building on free software, why is he in the business of making WordPress themes? It seems odd to blame WordPress for putting pressure on people to use the license that's helped to make WordPress so successful.
Though, maybe I haven't witnessed much of the public bashing. I guess, depending on how they go about shaming devs in violation, well, there might be better ways to do it (i.e. privately before publicly...). I'm not involved enough in the community to know much about those methods.
"If those venues really cared about the arts, and really appreciated what artists and musicians bring to their locales, then they would be sure to help cultivate a society that is supportive of the arts. That is - a society that is not hesitant whatsoever to cough up a few bucks to support open mics, performing musicians. Venues can pay their BMI & ASCAP fees out of a percentage of those proceeds."
What percentage of those ASCAP/BMI fees actually goes to musicians playing at open mics?
Of the money that goes to artists (and I know how little of it there often is—I play at these venues), why should that be paid out to collection societies to be distributed to artists with the most airplay, as opposed to given directly to the local musicians who are actually performing?
"unlike the us, the canadian constitution doesnt suggest absolutely unlimited free speech rights, and as such, limiting "fair dealing" does not violate any rights."
The Supreme Court of Canada has ruled that: "The fair dealing exception, like other exceptions in the Copyright Act, is a user's right. In order to maintain the proper balance between the rights of a copyright owner and users' interests, it must not be interpreted restrictively."
The digital lock provisions in Bill C-32 would undo any fair dealing exceptions. Mike's not imposing a U.S. mentality, he's just point out what's common sense, and what current Canadian law and the Canadian Supreme Court have affirmed.
I don't think your morals are compromised. I use all kinds of proprietary crap, like the Mac and Flash software I used to make "Sita" in the first place. As a consumer, I often choose convenience - it's what we consumers do!
As an artist ("content creator") I was given an unusual opportunity to endorse or refuse DRM'ed distribution of "Sita." You're not in that situation at all.
I think your decision not to accept DRM was heroic, but I'm not sure I follow you here. How do you distinguish between an endorsement of creation tools (Mac / Flash) and an endorsement of distribution tools (Netflix with DRM)?
Aren't you making a statement as an artist and a creator—and not just a consumer—in terms of what tools you endorse or refuse in creating your art? Why is it only distribution that poses a challenge?
"The hotel is the one offering rooms to "the public" and including entertainment in the package. That's why it's being called a "public performance".
Blockbuster makes videos available to the public to rent, but does that make watching a movie in your basement a public performance? Record stores sell CDs to the public, but does that make listening to a purchased CD a public performance? And what about the car example? Should auto makers pay royalties because they sell cars to the public with entertainment systems in them?
It's not a matter of who the customers are. The question of public performance should have to do with the nature of the actual performance.
Copy right owners are granted 6 exclusive rights. The 6th right is "in the case of sound recordings, to Publicly Preform via Digital Audio Transmission." This applies to any digital streaming or download process... Any sort of digital transmission of audio constitutes a public performance.
When you watch a movie that has music in it on DVD, is that a digital audio transmission? How about when someone listens to a song off their hard drive in iTunes? That's definitely digital audio being transmitted, nevermind the transmission that would occur in a download, or a purchase from the iTunes store. What happens if you listen to a digital audio file from your basement, that's actually stored on a hard drive upstairs, and transmitted through a local area network? Do you require a license from a PRO?
What's the difference, with respect to royalties, between the digital audio transmission that takes place when you watch a DVD on an Xbox 360 versus when you play a game on it?
It's an insane, uninformed or incredibly intellectually dishonest thing to say, that any sort of digital transmission of audio is a public transmission of audio. The public part matters.
Unfortunately, I'm not too surprised. Charlie Angus is great when it comes to combating draconian legislation that serves to prop up outdated business models, or that mentions VCRs, etc., but his own suggestions are very much on the collective licensing side of things -- whether that means paying royalties at the ISP level or through more levies. He's more a supporter of new collection methods than new business models. I'm not surprised, but I am disappointed that he'd actually act on this without realizing what a bad idea it is...
"I don't think this is another case where we should be debating USA versus Canada"
In the post, or in the comments? I don't think it's a USA versus Canada thing. I'm a proud Canadian, but I think the USA has more reasonable laws when it comes to third-party liability (nevermind the whole human rights tribunals thing...).
"... especially comparing internet safety related laws."
This isn't about Internet safety. It's about free speech, and third-party liability. Section 13 has such a low bar, and without safe harbours it can threatened neutral platforms in additional to the people who are actually saying controversial things on them.
"It is obvious that both sides (all of NA) weren't ready for these types of concerns, so now we have to play catch-up. So why not together?"
Yeah, I think Canada would do well to look at the laws in the US around safe harbours.
"Songwriters don't OWN their songs (nice strawman), they own the exclusive rights to their work for a period of time as set by law."
Yes... that's the point.
"Nice try, but you need to learn from your boss how to be sarcastic better, you pretty much failed."
Um... you need to talk to songwriters and people in the music industry more. I was just repeating an argument I received yesterday on a folk music mailing list. It's an argument used all the time by lots of songwriters and musicians (and by record industry execs when they try to represent songwriters and musicians).
There was no imagination in my comment. I was just relaying what I've heard a million times from friends and acquaintances.
On the post: Ontario Premier Says Cellphones In Class Could Be Useful
Re:
Your comment might have been set to HTML instead of Plain Text? Plain Text automatically spaces lines when you do, with HTML you have to make the spacing explicit in HTML.
Good points though.
On the post: Ontario Premier Says Cellphones In Class Could Be Useful
Re:
On the post: Ontario Premier Says Cellphones In Class Could Be Useful
Re: There is zero NEED for cell phones in school class rooms.
What Ron said. Plus, this really has less to do with "cell phones" and more to do with mobile, handheld computers (even though McGuinty still calls them cell phones).
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: Re: Re: Re: Re: Re: Re: the GPL is dead, it just does not know it yet
Yes, but the FSF still considers public domain software and non-copyleft (e.g. MIT, BSD, or Apache licensed) software to be free software, even though there's no legal requirement for people to release the source code. The source code must be available for software to be consider free, but it doesn't have to be a requirement of the license for the software to be considered free.
You're not going to be proven wrong there, because all of the strength of the GPL does come from copyright. But what I'm arguing, and what Bradley Kuhn explains, is that GPL enforcement is only a tactic, not a goal. That is, having a way to reverse copyright and create requirements for freedom is a clever hack on a broken system. But, there are other ways to make the source code available. Kuhn suggests that source be registered with a copyright registration, and then released to the public when copyright expires (assuming a reasonable time frame were adopted).
But, there are also social tools and practices that can be used to make source code available. We can already see how that's done with permissive non-copyleft licenses. Often, the reasons to contribute source code are social or practical. Apple and Google both contribute to WebKit, because they want it to be strong for Safari and Chromium.
Now, clearly, there are problems still from a free software perspective, as both companies bundle up that free code into proprietary browsers. But you can see how a more reasonable copyright law could solve some of the problems. Apple's model would still present a challenge, whereas Safari is a proprietary browser built on an free software rendering enginer. But Chromium, which is free software, gets packaged up by Google as Chrome, which is not free software. But the code is essentially the same, minus the branding and the license. With a more reasonable copyright law, Chrome's license becomes even less of an issue from the perspective of free software.
I'm not saying that I know how the challenge would be overcome... but there are ways to create positive incentives for companies to share source code, even companies that are extremely proprietary like Apple, or companies that want to built proprietary products off the free base, like Google. The GPL takes advantage of copyright to create a strong legal incentive, but there could be other innovative ways to create incentives without depending on copyright.
Another social way might be with consumer pressure (though, it's a bit of a pipe dream now). For example, I don't think many people would buy a screwdriver from Home Depot if it came with a ridiculous EULA, could only be used with Home Depot screws, and you weren't allowed to switch the bits yourself... people just wouldn't be stupid enough to give away their freedom to use their own tools like that. Generally, they'd buy a screw driver they could own. The FSF tries to explain the value of software freedom in that sense too. For a business, there are practical benefits to controlling your own tools, to have a selection of vendors that can provide support or a wide range of developers you could hire to improve the software. For an individual, there can be benefits to "owning" (i.e. being in control) of software rather than just licensing it as well.
I guess what I'm trying to say is that there's a positive re-enforcement approach that's possible too. The GPL gets its power fully from copyright, but there are other ways to encourage people to release source code, and the weakening of the GPL would be a small trade for a more reasonable copyright law.
(Sorry for the length and rambling nature of the comment... hope I'm making sense!)
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: There are two arguments here
Agreed that the interesting legal arguments around the main quesiton -- are themes subject to the GPL? -- were buried. I was trying to keep the post on a level of a decent summary, without getting too deep into the legalities. I could have done a better job of highlighting the legitimate legal opinions that aren't in agreement with the SFLC. Pearson's reliance on those arguments was kind of lame, given that he'd subclassed and copied from the WordPress codebase.
I'm not sure what to think of the legal arguments. I think there is a huge amount of grey area. It likely would depend on a specific analysis of the code of any given theme... though, I think it's unlikely that the PHP code in many themes is that separable, or written entirely from scratch (as opposed to derived from another GPLed WordPress theme). But there are lots of legal challenges that could be made around interoperability and fair use.
But, even the SFLC said the GPL wouldn't apply to JavaScript or CSS, which does make a theme fairly useless in many ways, hence the continued WordPress.com policy of only promoting commercial themes that are 100% GPL (which implicitly acknowledge that fact that there's nothing wrong with selling GPL code, even if some in the community don't quite get that—there's nothing unethical about making money off free software, I think the accusations were around profiting from a potential license violation).
I agree that there's a moral, and a pragmatic and social argument to be made for encouraging fully GPL themes and extensions. I support the WordPress.com policy to only endorse GPL code, and other project websites, like drupal.org, do the same. It's better for the health of the ecosystem if extensions to the platform provide the same freedoms of the platform itself, otherwise you can run into lock-in at the plugin/theme level, for example. So, even if the legal argument for themes being subject to the GPL is weak (and at best with the SFLC's opinion, it still only applies to the PHP), there are other reasons to apply social and business pressure to theme (and plugin) developers to go GPL.
Good call. The legal and moral/social arguments could be better separated. I don't think anyone representative of WordPress.com is suggesting that it's bad to make money from themes though, they even list commercial themes as long as they're 100% GPL.
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: Opinions and Facts
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: Re: Re: the GPL is dead, it just does not know it yet
I urge you to read Bradley Kuhn:
http://www.ebb.org/bkuhn/blog/2008/04/10/gpl-not-end-in-itself.html
Copyleft is a jujitsu move. Though jujitsu depends on using the force of your opponent against him, it doesn't mean that you want your opponent to attack you.
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: the GPL is dead, it just does not know it yet
I don't get the argument that since the GPL relies on copyright it can't do a good job of undermining overly restrive copyright. It's just a means to an end, while copyright law is out of whack. It's not necessary at all for free software, just often a useful tactic while restrictive copyright is the default.
Bradley Kuhn debunks this better than I: http://www.ebb.org/bkuhn/blog/2008/04/10/gpl-not-end-in-itself.html
And the GPL is a hack (I didn't say "hack job"), but so is the Apache license. They both have their strengths and weaknesses, as far as removing the barriers of restrictive copyright go.
And other licenses being more popular than the GPL? Do you have anything to back that up?
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: Re: tow the wordpress line
Second, distributing non-GPL themes (I assume that's what you meant) and extensions harm WP in the sense that WP is built on software freedom; it was born from the ability to fork a codebase, and relies on that freedom to develop and grow. Non-free extensions to WP are corrosive to an environment of software freedom, because you start hitting dead ends, or getting non-free dependencies that would thwart the ability for users to practically exercise their freedoms. But, except in cases like that of Chris publicly claiming that WP's license doesn't apply to him (but his license should apply to everyone else), legal action would be a lot more divisive.
The fact that they haven't sued anyone isn't evidence that proprietary themes aren't harmful, it's just evidence that they're using proportional means. Legal action should be a last resort.
I think the claim that they resort to public shaming too quickly is more relevant, because some developers just might not understand the requirements of the GPL. Any examples, outside of Thesis, that you can point to of WordPress being too quick to put public pressure on devs (i.e. before doing so privately)?
On the post: Lawsuit Averted As WordPress and Thesis Settle Differences Over Themes And The GPL
Re: Re: Re:
Legally untested, maybe, but pretty widely agreed upon by legal experts who work with free software licenss. If Chris really thought it was such a flimsy legal argument, what difference would it make that he was subclassing or copying and pasting WordPress code?
And WordPress isn't alone in taking that stance. Everything on drupal.org must be GPL, including modules and themes, for example. And, I think it's a good idea that, even if only the PHP portion of WP themes are likely to technically be required to be GPL, WP only endorses themes that are fully GPL. That way you know you have the freedoms to study, use, modify and redistribute everything from wordpress.org, rather than having to pluck out proprietary parts of a theme from DIYThemes or someone.
Really, if Chris doesn't want to be work with the GPL or building on free software, why is he in the business of making WordPress themes? It seems odd to blame WordPress for putting pressure on people to use the license that's helped to make WordPress so successful.
Though, maybe I haven't witnessed much of the public bashing. I guess, depending on how they go about shaming devs in violation, well, there might be better ways to do it (i.e. privately before publicly...). I'm not involved enough in the community to know much about those methods.
On the post: How ASCAP And BMI Are Harming Up-And-Coming Singers
Re: BMI & ASCAP
What percentage of those ASCAP/BMI fees actually goes to musicians playing at open mics?
Of the money that goes to artists (and I know how little of it there often is—I play at these venues), why should that be paid out to collection societies to be distributed to artists with the most airplay, as opposed to given directly to the local musicians who are actually performing?
On the post: Canadian DMCA Introduced; Digital Lock Provision Trumps Any And All User Rights
Re:
Man, do your research.
http://en.wikipedia.org/wiki/CCH_Canadian_Ltd._v._Law_Society_of_Upper_Canada#Fair_deal ing
The Supreme Court of Canada has ruled that: "The fair dealing exception, like other exceptions in the Copyright Act, is a user's right. In order to maintain the proper balance between the rights of a copyright owner and users' interests, it must not be interpreted restrictively."
The digital lock provisions in Bill C-32 would undo any fair dealing exceptions. Mike's not imposing a U.S. mentality, he's just point out what's common sense, and what current Canadian law and the Canadian Supreme Court have affirmed.
On the post: Nina Paley: My Decision To Turn Down Netflix Due To DRM
Re: Re:
I think your decision not to accept DRM was heroic, but I'm not sure I follow you here. How do you distinguish between an endorsement of creation tools (Mac / Flash) and an endorsement of distribution tools (Netflix with DRM)?
Aren't you making a statement as an artist and a creator—and not just a consumer—in terms of what tools you endorse or refuse in creating your art? Why is it only distribution that poses a challenge?
On the post: Google Sued For Using The Term 'Gadgets'; Tiny Company Afraid People Will Think They Support Google
Inspector Gadget
On the post: Cablevision Buying Blogs... Will It Lock Them Up Behind A Paywall Too?
Torontoist
On the post: Irish Collection Society Wants Hotels To Pay Performance Fees For Music Played In Guest Rooms
Re: Re: Public?
Blockbuster makes videos available to the public to rent, but does that make watching a movie in your basement a public performance? Record stores sell CDs to the public, but does that make listening to a purchased CD a public performance? And what about the car example? Should auto makers pay royalties because they sell cars to the public with entertainment systems in them?
It's not a matter of who the customers are. The question of public performance should have to do with the nature of the actual performance.
On the post: ASCAP Thinks That Video Game Providers Should Pay Music Performance Royalties
Re: This entire article is completly off
When you watch a movie that has music in it on DVD, is that a digital audio transmission? How about when someone listens to a song off their hard drive in iTunes? That's definitely digital audio being transmitted, nevermind the transmission that would occur in a download, or a purchase from the iTunes store. What happens if you listen to a digital audio file from your basement, that's actually stored on a hard drive upstairs, and transmitted through a local area network? Do you require a license from a PRO?
What's the difference, with respect to royalties, between the digital audio transmission that takes place when you watch a DVD on an Xbox 360 versus when you play a game on it?
It's an insane, uninformed or incredibly intellectually dishonest thing to say, that any sort of digital transmission of audio is a public transmission of audio. The public part matters.
On the post: Surprising: Charlie Angus Proposing iPod 'You Must Be A Criminal' Tax In Canada
Not too surprising
On the post: Canadian Human Rights Tribunal Declares Internet Hate Speech Law Unconstitutional
Re: USA and Canada
In the post, or in the comments? I don't think it's a USA versus Canada thing. I'm a proud Canadian, but I think the USA has more reasonable laws when it comes to third-party liability (nevermind the whole human rights tribunals thing...).
This isn't about Internet safety. It's about free speech, and third-party liability. Section 13 has such a low bar, and without safe harbours it can threatened neutral platforms in additional to the people who are actually saying controversial things on them.
Yeah, I think Canada would do well to look at the laws in the US around safe harbours.
On the post: SOCAN Tries To Keep Its Copyright Consultation Submission Offline And Secret, But Fails
Re: Re: Re: Re: Re:
Yes... that's the point.
Um... you need to talk to songwriters and people in the music industry more. I was just repeating an argument I received yesterday on a folk music mailing list. It's an argument used all the time by lots of songwriters and musicians (and by record industry execs when they try to represent songwriters and musicians).
There was no imagination in my comment. I was just relaying what I've heard a million times from friends and acquaintances.
Next >>