Author Puts Article Online, Insists That Due To Copyright, You Cannot Link To It
from the that'll-work dept
BeeAitch points us to yet another misunderstanding of copyright law, though this one is more amusing than anything else. It comes from an article from 2005 written by one Dr. T. Matthew Ciolek, from Australian National University, and it's apparently about "trade routes." Honestly, it doesn't matter what the article is about. What matters is that at the very top, it says:Note: due to copyright restrictions this page may not be linked from other online pages.Then, at the very bottom, it says:
Copyright (c) 2005 by Encyclopedia of Globalization. Grolier Academic. All rights reserved. This page may not be linked from other online pages.And, in neither case is that accurate. You absolutely can link to it as I have just now (and above) and (what the hell) will do again (just for fun). Sorry Dr. T. Matthew Ciolek, that's just not how copyright works. You are free to block anyone who comes via referrals from other sites (or block referrals from this site specifically). You're also free not to post your content online, or to bar others from republishing it (recognizing certain legal exemptions). But, nothing in copyright law says that you can order people not to link to your work.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: copyright, links, t. matthew ciolek
Reader Comments
Subscribe: RSS
View by: Time | Thread
:p
[ link to this | view in chronology ]
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
What's the point of the URL at the bottom?
Inquiring minds want to know....
Chris.
[ link to this | view in chronology ]
Re: What's the point of the URL at the bottom?
Which I believe is of dubious legality.
But honestly, couldn't Masnick have used this thing called "email" and clarified the issue with Ciolek so we'd have the full story?
Then again, obtaining clarity wasn't what Masnick's post was really about, was it?
[ link to this | view in chronology ]
Re: Re: What's the point of the URL at the bottom?
[ link to this | view in chronology ]
Re: Re: What's the point of the URL at the bottom?
The linked to paper clearly claims, as indicated in this post, that links are not allowed. This post then points out that the claim is delusional. I'm not sure where your confusion originates, but possibly you are just making excuses for the person. Perhaps you could email them and clear up your confusion for yourself.
[ link to this | view in chronology ]
Re: Re: What's the point of the URL at the bottom?
So you did not obtain clarity prior to posting this? Looks like something Mike would do.
[ link to this | view in chronology ]
Yes, because referencing/citing someone else's work can be considered infringement. (must I put a /sarc?).
Not sure how that promotes the progress.
[ link to this | view in chronology ]
I had a coworker bring me a similar situation where she wanted to quote a sentence from a website that was reporting some statistics that were relevant to the report she was writing and that she was going to post online. But she was wary of the copyright notice on the website which stated that any reproduction of any aspect of the website without express written permission was a violation of copyright laws and violators would be subject to civil and possibly criminal prosecution.
I laughed and explained to her about fair use, about how statistics themselves cannot be copyrighted, and about how the copyright laws are so fucked up that there's no liability placed on parties that misconstrue what their rights are under copyright. They could put up a copyright notice that states that you owe them your first born if you copy any of their content and there's no repercussions for such misrepresentations.
[ link to this | view in chronology ]
Someone should inform Richard Stallman, because this is the exact assumption he makes in the GPL. A dirty little secret of the copyleft advocates is that many of the cases they claim their licenses cover go well beyond copyright's bounds. What's good for the goose...
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
According to the GPL and the FSF's interpretation of it, if I write software 100% by myself and it links dynamically to someone else's GPLed library, and then I give it to you, I have created a derivative work of that library and am bound by the GPL.
Even if I wrote 100% of the code myself. Even if I never give you a copy of the library.
Would you consider Mike's article above a derivative work of Dr. T. Matthew Ciolek's? After all, he linked to Ciolek's article. You need Ciolek's article to fully interpret Mike's. Should Ciolek be allowed to control Mike's ability to write or disseminate his article?
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
The purpose of IP law is (should be) to expand the public domain and to expand freely available works. So if someone wants to release works only under the conditions that derivative works also be freely released the law should support this. After all, it sorta expands the public domain, or at least the spirit of the public domain. If someone else doesn't like it, he doesn't have to use those works and can find someone else's work to use. No one is rightfully entitled to restrict others from freely copying and so the request to restrict such restrictions should be legally supported.
It should also be noted that there is a difference between free speech and software. Using, and linking to, someone's work as part of fair use exists to ensure free speech and to ensure that our free speech isn't hindered so that we can better express our positions and concerns, criticisms, or support for the positions of others. The importance of free speech, something that doesn't apply with software so much, should take precedence over licensing when compared to something like software.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
and to expand on this, the principles behind the GPL don't require government to exist. They can exist perfectly fine without government. The GPL simply says that people can freely copy as they please, no governance is necessary to govern this. It's copy protection laws that require government to exist. and the government can simply place limits on what it will protect. In the case of the GPL, there is no need for the government to intervene and place any limits on anything, because the GPL doesn't ask for any government to do anything since a government isn't needed to allow people to freely copy one another. It's the copy protection holder that's asking for special government privileges and the government can decide which privileges it doesn't want to grant. (well, the GPL does compel one to release the source code of derivative works, which may require government to enforce, and that aspect can be disputed separately since that's not the aspect I'm disputing).
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
http://en.wikipedia.org/wiki/Fair_use
By reading that, it's clear that fair use far more strongly applies to things like speech than code. The law says so. That's what the law says. Sorry that you don't get to decide what the law says and that the law doesn't say exactly what you want it to say, but that's tough.
"Examples of fair use include commentary, criticism, news reporting, research, teaching, library archiving and scholarship.
...
17 U.S.C. § 107
'the fair use of a copyrighted work, ... for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright. In determining whether the use made of a work in any particular case is a fair use the factors to be considered shall include:
the purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit educational purposes; ...'
Fair use, it's the law.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
You call me an IP maximist, yet it is Stallman and the copyleft brigade that want to use copyright law to tell me what I can and can't do with my own code. I argue that no derivative work is created, so I need no fair use defense.
You also argue that Microsoft, if they so chose, could sue every creator of a Windows program for copyright infringement for creating and distributing unauthorized derivative works, and that they would win because no court has recognized a fair use defense with respect to code. I find your IP maximist position interesting.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
No, because that's not how they license their operating system. If they did, then I might agree. In fact, if you look at things like Playstation 3, the courts have sided with Sony on this issue (though I would disagree with what the courts did here). When people try to hack things like Ti Calculators, courts might side with TI. Apple has had a past of very strict licensing with their operating systems and their early computers and processors and this has traditionally deterred people from adopting it. But if Microsoft did that, people will likely find another operating system to build code on.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
And you call ME an IP maximist?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Fair use/free speech defense, something that code isn't so much subject to.
I think one can also make a reasonable 'promote the progress' defense, though that hasn't been tried in courts so much. One can also make a reasonable 'citation' defense, books cite other proprietary books all the time and I never seen a court rule against that. I think there is a legal difference between using (or, as you call it, linking to) someone's code and simply referencing someone's speech. So, no, fair use isn't the only argument. You might personally classify them the same but, from a legal perspective, I would argue that 'linking' to someone's code is simply using it whereas 'linking' to a source of information is simply referencing it (and I do think the law should make that distinction), which has traditionally been very accepted behavior long before the Internet and computers.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
the courts HAVE already indicated that I can write all the code I want for my own device.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
You can do whatever the heck you want with your code, but when you take 'their' code and use it, you simply can't tell others what to do. Copy'right' is government intervention. IP maximists want more government protectionism. Restricting how you can restrict others doesn't require government since copying is something that doesn't need government. So, indeed, you are the IP maximist, you are the one that wants more government protection.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Or maybe I do want to distribute the source, but only to one partner under a contract that doesn't let them distribute it further. You're saying I should not be able to enter into that contract with a willing party?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
You willingly used GPL code and entered into a 'contract' with the code authors to use their code. If you don't agree with their terms, then don't use their code.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
http://lwn.net/Articles/61292/
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Ignoring that bit of nonsense, "implicit agreement" my ass. What I am concerned about are my legal obligations and constraints. Specifically, what can Ciolek prevent Mike from doing and what can Stallman prevent me from doing.
Ciolek says that Mike cannot link to his article. So they have an implicit agreement and Mike should honor that?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Addressed in my next post. The GPL license is a legal obligation because the law sees licenses as something that everyone must follow. The law doesn't see simply referencing other works as requiring a license and a link is simply a reference to someone else's work.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Here is more on linking.
"the court in Ticketmaster v. Tickets.com found that links were not infringements of copyrigh"
http://www.chillingeffects.org/linking/faq.cgi
So, if I intentionally linked to infringing material to induce infringement, then I can get in trouble. but if you, the copy privilege holder, willingly put a website up and I linked to it, then I'm good. Every situation is different and to lump code with hyperlinks is a bit disingenuous.
and if you still think you're right
"On about Aug 03, 2010, BusyBox won triple damages of $90,000 and lawyers' costs and fees of $47,865, and possession of "presumably a lot of high-def TVs" as infringing equipment in the lawsuit Software Freedom Conservancy v. Best Buy, etal., the GPL infringement case noted in the paragraph above.[29]"
http://en.wikipedia.org/wiki/BusyBox#GPL_lawsuits
IOW, the law disagrees with you. The GPL is enforceable, but hyperlinking is generally OK.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
http://en.wikipedia.org/wiki/GNU_General_Public_License#The_GPL_in_court
The whole section is worth reading, but in particular
"the court noted that "the GPL encourages, rather than discourages, free competition and the distribution of computer operating systems, the benefits of which directly pass to consumers".[55]"
IOW, the promote the progress argument and the purpose of IP law argument is, indeed, a valid one that courts do consider.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
What I said was, if I write code on my own that dynamically links to a GPLed library, and then give it to you in source or binary format, and I never give you the GPLed library at all, there is no part of copyright law that obligates me to do anything. The GPL cannot be enforced on me or my code because I have created no derivative work.
Stallman and the FSF want an extraordinary, some would say "IP maximist," definition of derivative work to be applied to me that would make my code a derivative work of the library even if I just refer to it and I distribute no part of the library. I point out that this Maximist position is very similar to the one taken by the author of the article Mike linked.
Worse yet, the ramifications of such a maximist position would be disastrous for the software industry and the open-source movement.
I am arguing that for the same reasons that Ciolek's IP maximist views should not be tolerated, neither should Stallman's.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Certain aspects of your code require the library to work. But he's not restricting you from developing and redistributing the works, he is only restricting you from restricting others. That's hardly a 'maximist' approach, its' a minimist approach, since the freedom for others to copy and redistribute your work exists outside of copy protection laws and outside of government (aside from forcing you to distribute your source code, but that's hardly a maximist approach when compared to the desire to lock your code down under licenses that use the law to restrict unpaid for redistribution).
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Furthermore, Stallman gets to do this, but nobody else (e.g., a proprietary software vendor) does because they have a different agenda?
Guess the ends justify the means but only when it comes to Free Software.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
He's not 'expanding' it, he's merely using the already existing definition.
"Furthermore, Stallman gets to do this, but nobody else (e.g., a proprietary software vendor) does because they have a different agenda?"
Who said that? If it were up to me, nobody would have copyright and the GPL won't be needed. I would abolish IP, or substantially limit its scope and time length.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Since the GPL is not a contract, the question is: what law prevents me from distributing my code in binary form only, or alongside a restrictive contract of my own? Stallman and the FSF say "copyright law." But it's my code. My copyright.
"Ah, they say, but your code is a derivative work of our code!"
And there lies the question. Why is my work derivative of theirs?
Because it incorporates their code? No, it doesn't.
Because it requires their code to run? That is tougher. Consider the GPLed math library FFTW. The proprietary Intel MKL library implements identical interfaces, to the point where I can dynamically link to either one without changing a byte of code. Which is my program a derivative of, then?
Further, if "I need X to run, therefore I am a derivative of X" has utterly disastrous consequences. Everything becomes a serivative of everything else. Do PC BIOS vendors then become infribged upon by every piece of PC software?
You argue that proprietary vendors prohibit linking, but not using the same legal mechanisms the GPL does. They use licenses (which, like the GPL, may be limited in scope themselves by derivative works boundaries). They sometimes use clickwrap or shrinkwrap agreements, which are in a legal gray area but may be contracts and not licenses.
Further, this has not been well-tested in court. The MMOGlider case is informative. There, the lower court initially agreed that MMOGlider violated copyright (and it probably did more than linking), but the appeals court reversed this, stating that copyright was NOT violated, only the EULA, which was a contract. The GPL is explicitly not a EULA.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
end-user licensing agreements.
http://en.wikipedia.org/wiki/Software_license_agreement
It's a license.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
When Sony licensed their PS3, they decided that they can restrict third party software. They licensed it under those terms (and when people decided to jailbreak the PS3, the courts sided with Sony). Same thing with Xbox.
http://www.techdirt.com/articles/20101022/04205511542/jailbreaking-your-iphone-legal-jailbr eaking-your-xbox-3-years-in-jail.shtml
Apple tried to claim that jail breaking their products is a violation (and I remember Motorola claiming something similar as well). So the answer is, it depends on the licensing terms. It's not infringement if the license permits it. But if the license is too restrictive, who's going to buy the product?
http://www.techdirt.com/articles/20090213/0326103758.shtml
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Without technological protection measures, which would probably not be permitted by the GPL either way, the DMCA doesn't matter.
Beyond that, it depends largely on what is being modified, and who is doing the modification to see what exclusive right of copyright would be violated. To my knowledge none of this has been fully adjudicated.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
No, it is an issue. When you ask the question, "Do PC BIOS vendors then become infribged upon by every piece of PC software?" No, because they license their hardware in such a way that allows third parties to write software on it, unlike how Sony licenses their Playstation 3. See.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Sony alleged DMCA violations that led (at least) to copyright infringements of firmware. As far as I know Sony never argued that the violation was just calling existing code - it was the creation of modified versions of code. This is completely different. Also, the Sony case settled, so it is totally unclear they would have prevailed on that argument. Like Stallman, they can make whatever expansive arguments they want about the bounds of copyright law. Doesn't make them true.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
There are all sorts of licensing agreements behind the scenes.
"The vast majority of PC motherboard suppliers license a BIOS "core" and toolkit from a commercial third-party, known as an "independent BIOS vendor" or IBV. The motherboard manufacturer then customizes this BIOS to suit its own hardware."
http://en.wikipedia.org/wiki/BIOS
Bottom line, there is nothing in the licensing that prevents people from creating software on their computers.
Regarding the sony cases, the judge largely sided with Sony in most cases.
http://www.techdirt.com/articles/20110127/17101112863/sony-ps3-hacker-gagged.shtml
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
According to you, copyright law itself prevents this. So the licensing has to explicitly permit it. And you're the one running programs on the computer, so an upstream license between your board vendor and your BIOS vendor grants you no rights. But let's assume there is one: then, you should be able to show me the license from your motherboard vendor allowing you to create derivative works of the BIOS as per their agreement with the BIOS vendor, right?
Of course it's rapidly become clear you're just reading three sentences from Wikipedia, deciding that sounds good to you, and making wildly bullshit legal claims with no understanding of the content or mechanism of the law.
At the same time, you have advocated massive expansion of the scope of copyright law, increased "induced infringement" scope, and the ability for software vendors to create and enforce tgeir own interpretations of copyright law in accordance with their agendas.
Bravo! I have leaned the secret of making IP minimalists betray their entire belief system. Offer them monopoly privileges to use for copyleft, and then point out that those privileges may be limited. They'll be out there picketing for broader monopolies post-haste.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
According to you, copyright law itself prevents this. So the licensing has to explicitly permit it. And you're the one running programs on the computer, so an upstream license between your board vendor and your BIOS vendor grants you no rights. But let's assume there is one: then, you should be able to show me the license from your motherboard vendor allowing you to create derivative works of the BIOS as per their agreement with the BIOS vendor, right?
Of course it's rapidly become clear you're just reading three sentences from Wikipedia, deciding that sounds good to you, and making wildly bullshit legal claims with no understanding of the content or mechanism of the law.
At the same time, you have advocated massive expansion of the scope of copyright law, increased "induced infringement" scope, and the ability for software vendors to create and enforce tgeir own interpretations of copyright law in accordance with their agendas.
Bravo! I have leaned the secret of making IP minimalists betray their entire belief system. Offer them monopoly privileges to use for copyleft, and then point out that those privileges may be limited. They'll be out there picketing for broader monopolies post-haste.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Agreements can be implied, they don't always have to be express. If Sony and various router and phone manufacturers can restrict what one can do on 'their' hardware, then bios manufacturers can do the same. and hardware generally isn't subject to copy protection laws anyways. The software has downstream licenses in such a way that, when I buy the computer or motherboard, there exists a reasonable expectation that I may build and install software on it. Not everything has to be express to be an implied agreement.
"Of course it's rapidly become clear you're just reading three sentences from Wikipedia, deciding that sounds good to you, and making wildly bullshit legal claims with no understanding of the content or mechanism of the law."
It's hardly a wild claim given our current laws. If you think so, why don't you take on the challenge to violate the GPL and see what happens?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
It was the mere creation of code that allows the PS3 to do what Sony doesn't want it to do that was a violation, and even posting a video showing people how to jailbreak it was considered a violation.
http://www.techdirt.com/articles/20110207/23320513000/sony-demanding-identity-anyone-w ho-saw-ps3-jailbreak-video-youtube.shtml
Remember, the jailbreak code was open source. So no one had to modify Sony code or create modified code, they created their own separate code and published it on the net. Yes, that code needed Sony's code to operate, but your code needs GPL code to operate just as well.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Moreover, if you got your wish and copyright were eliminated, software vendors could make modifications to the now public-domain code, release only the binaries, and keep the code fully private, restricting its distribution through contracts, trade secret law, or both.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I'm not sure I agree with trade secret laws, but the rest of what you said I'm fine with.
First of all, as it stands now, there is no public domain code for them to build upon. So copy protection abolition would be better in this regard.
Secondly, I have no problems with vendors keeping their source code private, they already often do that anyways, even with copy protection laws. So what's your point?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I hardly think it would be a substantial expansion. For example,
"a few courts have now held that a hyperlink violates the law if it points to illegal material with the purpose of disseminating that illegal material: "
http://www.chillingeffects.org/linking/faq.cgi
So, under limited circumstances, merely hyperlinking can be illegal. I would argue that it would hardly be a substantial expansion to say that this is one of those situations, since this sort of code linking undermines the purpose of the law and the license.
and courts have ruled that linking that induces infringement (ie: links to circumvention tools or links to videos that help teach people how to circumvent) can be in violation.
Other examples
" In the DeCSS case, Universal v. Reimerdes, the court barred 2600 Magazine from posting hyperlinks to DeCSS code because it found the magazine had linked for the purpose of disseminating a circumvention device. (See Anticircumvention (DMCA).) The court ruled that it could regulate the link because of its "function," even if the link was also speech.
In another case, Intellectual Reserve v. Utah Lighthouse Ministry, a Utah court found that linking to unauthorized copies of a text might be a contributory infringement of the work's copyright. (The defendant in that case had previously posted unauthorized copies on its own site, then replaced the copies with hyperlinks to other sites.) "
So it would hardly be a substantial expansion. Every case is different, there is no hard fast rule to linking and infringement. Your code linking could be considered infringement because it induces what is effectively an infringement, the use of GPL code working with proprietary code. If you build your code using GPL code and you included the code, that's an infringement, just like if someone included a Microsoft word document and included infringing copies of Microsoft word with the document (though Microsoft's license allows you to freely distribute Word documents by themselves, otherwise, no one would buy word :). Writing code with GPL code, deleting the GPL code, and encouraging others to separately download it has almost the same exact effect as writing code and distributing it with GPL code. When you write your code, you had to use GPL software to write your code. You couldn't write and test your code without such software. So when you do so, you must do so under their license, just like I have to follow Apple's or Sony's restrictive license when I use their software or hardware or their PS3. and the courts have ruled in favor of Sony when others tried to write separate code for the PS3. If Sony can limit what others can do with the PS3 and if they can limit the code they can write and redistribute, then the GPL can limit how its code is used just as well. It's hardly a stretch. People can't even redistribute their own code that they used to write for the PS3 or for a TI calculator or whatnot.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Likewise, trying to write GPL based code and encouraging people to download the code separately is merely a disingenuous circumvention of the GPL. It allows you to benefit from the GPL without following its terms.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
The GPL's terms apply to (and can necessarily only apply to) derivative works. Use of some library that I neither incorporate nor distribute creates no derivative work.
Further, linking proprietary and GPL code is not an infringement. The GPL allows this, although it is not clear that loading a program into computer memory is restricted by copyright law at all. The GPL controls only distribution. I therefore cannot be inducing infringement by telling users to do something that is perfectly OK.
I am happy to see Techdirtophiles are arguing in favor of increased "induced infringement" by the way. Very nice.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
If you are not violating its terms, then what's the problem? If you are violating its terms, then there is a problem.
"I am happy to see Techdirtophiles are arguing in favor of increased "induced infringement" by the way. Very nice."
I'm not Techdirtophiles and I'm not making an induced infringement argument. I'm merely pointing out that it won't be the huge stretch (from our current laws) that you make it out to be. Every situation is slightly different and the courts treat them differently from case to case.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
The problem is that the bounds of the license are wholly dependent upon the ambiguous definition of "derivative work" in copyright law. Thus, the license is ambiguous.
The FSF and Stallman have a very broad opinion about what the bounds should be. As drafters of the license and spokespeople for it, their interpretation influences the license's users.
Only courts and lawmakers can resolve the ambiguity. Neither has. I believe that the FSF position is bogus, causing fear, uncertainty, and doubt and is inhibiting the freedoms of others to develop and release software in the manner of their choosing.
If Mike is going to make fun of this guy for his overbroad interpretation of copyright, why not point out and rectify a far more meaningful and pernicious example?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
No, your belief inhibits GPL developers to release software in the manner of their choosing. But I guess this only applies when it benefits big corporations.
"why not point out and rectify a far more meaningful and pernicious example?"
I agree that it is a meaningful example and the rectification should be that if you make works that use (or, in your terms, 'link to') GPL works, your works should be released under the GPL (provided that this is what the GPL requests, of course) and the law should mandate it.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
The GPL requires that derivative works be distributed under the GPL. It imports the definition of derivative work from copyright law. Thus, it is ambiguous. Even if it clarified its position, it would be limited by the bounds of copyright law.
Its creators interpret the ambiguity ultra-broadly in an attempt to exploit that ambiguity to further their own agenda. If you give them the power to set the scope unilaterally, you must also give that power to Sony and Microsoft and Apple, who will probably make you very unhappy with the breadth of their interpretations. You really want to make the law "you know, whatever the guy who wrote the license meant?"
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I believe your interpretation is a bogus attempt to undermine the GPL so that you can benefit from it without sacrificing anything of your own and without sacrificing your copy protection privileges. You are inhibiting the freedoms of others to freely copy the works that you built on top of the works of others.
and no one is entitled to the freedom of requiring others (ie: government, service providers) to police, abide by, and enforce their monopoly wishes.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Yep. Except it's not bogus, it's perfectly legal. Everyone here is always clamoring for fewer IP laws and greater limitations on them. Well, here's a good one. And now you don't like it because it prevents you from exerting control over others with the force of law. As I noted, giving the power to have copyright mean whatever he wants to Stallman means giving it to Sony also.
and no one is entitled to the freedom of requiring others (ie: government, service providers) to police, abide by, and enforce their monopoly wishes.
Including Stallman and the FSF. They want a monopoly on my code to enforce their agenda on me and my behavior. They don't get it. Wish granted.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Laws aren't needed to 'enforce' the absence of copy protection. Laws are needed to enforce copy protection.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Not so. You forget (or are ignorant of) your history.
Stallman invented copyleft because he only had a binary of a printer driver he wanted to screw with. He could not modify it without the source, and was mad that you could distribute the binary without corresponding source code.
In the absence of copyright law, Stallman's situation would have been...identical. The software vendor could have kept the source proprietary and not distributed it at all. To control employees going rogue and distributing it, they could use simple contracts - which they probably do anyway. You want to abolish contract law, too?
Stallman used the monopoly force of copyright to get a demand met: the distribution of code. No law, no mandate. And any limits on copyright apply to everyone - him included.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
"well, the GPL does compel one to release the source code of derivative works, which may require government to enforce, and that aspect can be disputed separately since that's not the aspect I'm disputing"
But, OK, if you're so confident that you're right, why not put your money where your mouth is. When Mike is convinced that he's right, what does he do? He actively defies the wishes of the opposition. When asked to take down content and he believes he doesn't legally have to, he doesn't. When asked not to link to a site, what does he do? He links to it, on purpose, just because a legal defiance (and to make a point, that it is, or at least should be, legal). When threatened with all sorts of legal threats, what does he do? He ignores them because he believes himself to be legally in the right.
and IP maximists have often tried to argue that people would be more than willing to challenge bogus legal infringement threats (ie: when it comes to these mass Righthaven anti-piracy suits that could potentially target non-infringers) if the alleged infringer didn't infringe because, you know, litigation isn't such a deterring process. So the same goes for you.
So why don't you use, or link to, GPL (not LGPL) code and release your proprietary code without source code. Do it. Link to it here. When someone then freely uses your code without paying, sue them. and don't settle. Let the judge decide. Post your code here and I'll notify the FSF and what have you to sue you just as well. and don't settle, let the judge decide. Put your money where your mouth is. Mike would, and in the past, he has, by ignoring all sorts of legal threats he thought had no merit. Mike is willing to do it. Why don't you, if you're so confident that you'll win and that the GPL's interpretation is a huge stretch. After all, the GPL authors are just FUD. If you're so confident that you're right and you stand on principle, why not back those principles up with action? Since you have the opportunity to initiate the first lawsuit, you even have more leverage to choose the initial court, which could mean you might even win the initial ruling (but could lose on appeal).
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Only if your code requires their code. Otherwise, write your own code and don't require theirs. It's that simple.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Isn't it the point of this discussion that doing what you just said would be a violation of the GPL (and you are arguing that it wouldn't/shouldn't be a violation of law)?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Linking to a library causes it to be loaded into the same memory space as your code, and the only reason to link to a library is to utilize and execute the code contained in it. You create a derivative work because the original code -exists in your program- at run time. If you don't like it, don't use GPL'd libraries, there are commercial alternatives, or - as you keep saying, you could simply "write 100% of the code yourself," in which case you would not link to any GPL libraries.
How about you stop using the word "link" when referring to libraries, and start using the more descriptive phrase "dynamically load code into the same memory space," since you can't seem to get around the fact that "linking" in a compiler does not do what you think it does.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
Is Mike's article a derivative work of Ciolek's or not?
If so, he needs a fair use defense or a license. You also disagree with Mike that there is nothing in the law preventing linking, and that some forms of linking that fail the four-factor test may be infringing.
If not, he needs neither and it is unclear why you keep blathering on about fair use.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
You can call it that, but it's not an infringing derivative work. Courts have ruled that hyperlinking is fine, but violating the GPL is not. Period. That's the law whether you like it or not. I don't care what you call it, linking, derivative works, etc... the point is that what Mike did is legal. The courts said so. Violating the GPL is not legal and the courts agree. Period. That's the bottom line, like it or not, it's what the courts have decided. What Mike did = legal. Violating the GPL = illegal. The courts agree.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
No, you're wrong. Period. You are wrong. Mike is right. The courts say that Mike can link. The courts say that GPL violations are a tort.
"What I am concerned about are my legal obligations and constraints. "
and I provided you with your legal obligations and constraints, with court cases to back them up. Courts have enforced the GPL. Courts have said that hyperlinking is OK. Those are your legal obligations and constraints. It's what the courts have said. Bottom line, you're wrong.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
"the court noted that "the GPL encourages, rather than discourages, free competition and the distribution of computer operating systems, the benefits of which directly pass to consumers".[55]"
IOW, the rational is partly what I said above.
As far as the linking case
"The court found that Tickets.com only republished the uncopyrightable factual data in Ticketmaster’s site on to Tickets.com."
http://ilt.eff.org/index.php/Ticketmaster_v._Tickets.com
Mere hyprlinks are not protected.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
Your argument about the purpose of copyright law does not give Richard Stallman permission to tell me what I do or do not have to do with code I wrote.
If I invoke fair use, then I can distribute my code however I want. Source, binary, obfuscated, encrypted, or otherwise. You agree?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
Hmm, let me add a correction here: ...Unless the law was enacted in such a way as to violate other laws - in my opinion that should invalidate the secondary law until such time as the terms are corrected.
[ link to this | view in chronology ]
Re: Re: Re:
When you "link dynamically" to a library in software, it is loaded into the same memory space as your program and executed when needed. (Vs. statically - having embedded it directly.) There is little difference in this case between static and dynamic linking from the end result - the code is brought into your program's memory space and executed just like the rest of the code you may or may not have written.
Now, to be honest - your argument is fallacious - as your software isn't written 100% by yourself. Why did you link to the library in the first place? Why, to utilize its code as part of your program to create your software solution. You didn't have to use someone else's code for it, but you chose to take the short-cut to the solution they offered you. You don't -have- to do anything, and your software isn't bound by any terms, until you decide that you want to share your new solution with someone that was based on the GPL'd solution you borrowed, directly, in your code. Then, all the GPL says is that since you found it so useful, and used the software (directly, I might add, in your own software) to solve your problem, you must provide the same liberties to anyone you give it to.
So, when you get around to writing 100% of your own software, you'll find that you don't link to anyone's libraries but your own.
A hyperlink is just an address on the internet.
[ link to this | view in chronology ]
Re: Re: Re: Re:
Not that I necessarily support copy protection laws for code, pictures, movies, etc... either.
[ link to this | view in chronology ]
Re: Re: Re: Re:
Or, I write a program that runs on Windows. Is my program a derivative work of Microsoft's?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
Your article would be meaningless even to you without the existence of the specified scene, and your program would not even be programmable without the underlying operating system. The fact that Microsoft choose not to restrict your use of their code does not mean your work is not derivative - it is still built on their work.
The fact is that licensing rules apply to any library - if you don't like the licensing agreement offered by one then don't use that particular one - there are plenty of others out there that will happily sell you a more restrictive license, or you can build your own.
[ link to this | view in chronology ]
Re: Re: Re:
Citation please
[ link to this | view in chronology ]
Re: Re: Re: Re:
http://www.gnu.org/licenses/gpl-faq.html#LinkingWithGPL
[ link to this | view in chronology ]
GPL/LGPL
I'm not sure why we even got off on this tangent; an HTML link and linking to an object code library are completely different things. Just because they both happen to use the word "link" doesn't mean they are equivalent.
[ link to this | view in chronology ]
Re: GPL/LGPL
Regarding HTML linking and software linking: there are clear parallels. There is the issue of what constitutes a derivative work. There is the issue of what kinds of references are permitted under fair use.
Regarding tangents, who the fuck died and made you the discussion moderator?
[ link to this | view in chronology ]
Re: Re: GPL/LGPL
Enforcing hyperlink protections is merely blocking factual data and factual data is not protected. The use of code =! factual data.
If you were to link to GPL code on a web page or reference the website or location in a document and tell someone about the code to encourage them to download it, that's just factual data. It's fine. But when certain aspects of your code use other code, that's not merely referencing factual data, it's requiring GPL code for certain aspects of your program to work.
[ link to this | view in chronology ]
Re: Re: GPL/LGPL
Sure and the courts have dealt with all that. The courts have basically decided that hyperlinking is fine. GPL violations are not.
[ link to this | view in chronology ]
Re: Re: Re: GPL/LGPL
One case raised the issue in pretrial motions where it was deferred to trial, which never happened. I imagine that more than one Free Software advocate would be quaking in their boots if the issue were to be decided in court, because the FSF's interpretation would go against nearly every other comparable interpretation of derived work that has been examined in non-software domains.
The result would be that the LGPL and the GPL would become more or less equivalent.
[ link to this | view in chronology ]
Re: Re: Re: Re: GPL/LGPL
https://en.wikipedia.org/wiki/GNU_General_Public_License#Linking_and_derived_works
ht tp://www.law.washington.edu/lta/swp/Law/derivative.html
http://stackoverflow.com/questions/189014 8/when-is-your-code-a-derivative-work
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: GPL/LGPL
However, I doubt that the person who brought up the issue wanted it addressed with facts.
Their attempt to link was lame.
[ link to this | view in chronology ]
Re: Re: Re: Re: GPL/LGPL
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
http://www.gnu.org/licenses/gpl-faq.html#LinkingWithGPL"
This does not address the issue you are attempting to raise.
[ link to this | view in chronology ]
Re: Re: Re:
Just want to make sure the basis of you argument is this ridiculous assertion.
[ link to this | view in chronology ]
Re: Re: Re: Re:
YHBT. YHL. HTH. HAND.
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
Not exactly. Your code can be 100% proprietary. What you cannot do is claim copyright over the linked code itself.
So, you would be free to distribute your work in whatever way you wanted to. What you could not do is distribute the linked code under your license.
See:
http://www.gnu.org/licenses/gpl-faq.html#Prelinking
Now, if your software requires the GPL library to compile (thus the GPL code will be included in the binary), then yes, you have to GPL your code. This is solely because the non-GPL, proprietary code cannot be released separately from the GPL code.
But if you can distribute your code (including the binary) separately from the GPL code, then you're under no obligation whatsoever. You can even write proprietary plug-ins to GPL software.
Incidentally, if you're merely linking to some piece of code, that code is quite possibly covered by the LGPL, which is quite distinct, and allows you to include those libraries in proprietary software. Just sayin'.
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
That's not actually what they say: "It depends on how the program invokes its plug-ins."
Stripped of the geek-speak (which I, in fact, do speak), it means basically what I said above. If the program can compile and run without any GPL code being included, then releasing that version under a proprietary license is fine. If, on the other hand, the program requires a GPL library to function at all, then the whole thing must by GPL.
And, of course, that doesn't apply to the LGPL at all (which many Linux "plug-ins" use, e.g. LADSPA).
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
Also, interfaces are not generally subject to software copyright. Just because there's a GPL DLL that implements AddNumber(int, int) doesn't mean that I can't write my own DLL that implements AddNumber(int, int). And it doesn't mean that I can't tell the user that he has to find his own library that implements AddNumber(int, int). And it doesn't stop me from suggesting that he try that GPL library over there which I am in no way giving to him.
It would be like if I invented a coffee-pouring robot that had instructions to walk to your bookshelf, find a copy of the book "Gateway", count the words in chapter 7, and pour you a cup containing that number of milliliters. This does not require me to have a license for the book "Gateway". It also does not require that the book be by any particular author or publisher (although even if it did, I would argue I'm still not violating anything.) It requires YOU to have the book, and it requires that the book have a chapter 7. If your copy of the book has an anti-coffee-robot license restriction, that is YOUR problem, not mine. It's irrelevant whether the robot breaks down if it can't find the book.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
You're arguing a point (or a few points) that aren't being disputed. It seems that your reading comprehension skills need some adjustment.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
Indeed, you could. Unless, of course, AddNumber was covered by patent laws - in which case you couldn't. That's why so many software engineers (including those in the FSF) oppose patents for code.
In any case - if you wrote some function, or plugin, or library or whatever; that does exactly the same thing as GPL code, except without using their actual source code - then you can release it however you want.
Think about the reverse situation. If that wasn't the case, the GPL wouldn't be able to write their own C++ compiler. Yet they did.
[ link to this | view in chronology ]
What. The. Fuck.
Same word, COMPLETELY different meanings. I cannot believe this has led to a thread so huge it went over the side of the page.
Linking, in the hypertext meaning, which is what Mike is talking about, is providing a way to go from one document to another. Nothing in copyright forbids this.
Linking, in the computer programming meaning, is combining several object files (basically, parts of computer programs) into one, resolving the references between them. There are two main variants: static linking, where the object files are combined into a new single file; and dynamic linking, where the same thing is done every time the object file or program is loaded. This combined file clearly is a derived work of the original files, and thus copyright applies.
[ link to this | view in chronology ]
Re: What. The. Fuck.
AFAIK .......
In the case of dynamic linking, when the originator of the code which makes use of the shared object does not provide same with their distribution they have not infringed upon the copyright of library copyright holder. The person executing code from originator needs to obtain the library themselves and obtain necessary licensing, etc. Code utilizing shared objects usually does not run well without the libraries.
There may be an issue as to whether the originator of code which makes use of the library has obtained the necessary licensing for that library which was used during development of their code.
btw .... IANAL
[ link to this | view in chronology ]
Re: What. The. Fuck.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re:
You are definitely wrong about this. For example, GPL is a copyright license.
Code is also, unfortunately, covered by patents (in some cases). This is much worse than copyright, since you can actually patent a process - so if your program does the same process as someone else's program, without sharing a single line of code, then you're infringing.
Of the two, patenting software is definitely worse, which is why the FSF (and many others) are so against it.
[ link to this | view in chronology ]
Re:
WOW. What a revelation. I never knew that. Dirty little secret indeed.
Thank for bringing that to our attention
P.S. Care to cite any examples in support of your argument? Thought not.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
reverse psychology SEO
[ link to this | view in chronology ]
Re: reverse psychology SEO
[ link to this | view in chronology ]
I clicked it
[ link to this | view in chronology ]
Re: I clicked it
[ link to this | view in chronology ]
The technology "made me do it" !!!
so you would rather see people NOT making their works available online (not post your content online).
So if they feel they cannot correctly how it is linked too, it is better that the information is not made available to ANYONE!!
Masnick we ALL know you are technically capable of linking to something.
Just like it is totally clear you are technically capable of shooting a gun.
Does your ability to be able to perform a task automatically give you the right (and responsibility) TO DO IT...
Masnick, go to your kitchen and prove to me you are capable of placing your face on a turned on Hot plate !!!.
I bet you can probably hit yourself over the head with a house brick as well,,,, love to see you try !!!!
Masnick you have the mind set that if you can do something, and it involved technology, you have a RESPONSIBILITY to do that thing.
With TOTAL disregard to ethics, morals or the LAW, if you believe technology can achieve something, it is your RIGHT, and REQUIREMENT to abuse that technology.
Yes, you CAN copy copyrighted songs.. technically
NO you cannot copy copyrighted songs ... LEGALLY/Ethicly,morally.
Yes, you CAN shoot a gun and kill someone - Technically
NO you can NOT shoot a gun to kill someone - ethically
Yes, you can technically make money by stealing off other people, or by selling "crystal balls".
Yes, you can also make money from the efforts and skills off other people technically..
But you cannot do it ethically, morally, or legally...
Just because you have the technology, the knowledge, and the incentive there is nothing in that, that means you have any legal, moral, ethical, or personal right to take that act.
You can technically do lots of things, just because you CAN does not mean YOU MUST, or are forced to do those things.
I am sure you car is capable of exceeding the speed limit, technically you can speed whenever you want, but if you are caught for speeding, are you going to use the excuse "THE CAR MADE ME DO IT"..
"Judge, the TECHNOLOGY MADE ME DO IT,,, I plead insanity"
[ link to this | view in chronology ]
Re: The technology "made me do it" !!!
You don't have to plead it, we already know.
[ link to this | view in chronology ]
Re: The technology "made me do it" !!!
Also, just as there's ways to prevent strangers from getting your home address, there's ways to prevent strangers from getting a web address. Copyright, however, is NOT one of them.
BTW, if you don't have a clue about a cars, you don't just jump in, drive however the hell you want, and then curse at everyone to get the hell out of your way. The internet works the same way (except you don't need a license). When you shout down others about the "right" way to use something that you have no clue about, you look like a fool--no one takes you seriously.
[ link to this | view in chronology ]
Re: Re: The technology "made me do it" !!!
[ link to this | view in chronology ]
Re: The technology "made me do it" !!!
You might be interested to know that I have actually taught at ANU and just sent an email to a few heads of departments asking WTF.
Linking to a web site anywhere in Australia is NOT, I repeat NOT illegal or unlawful under The Copyright Act, or any other statute UNLESS the material is material that would be classified as RC (Refused Classification) and even then it's a very very grey area.
Basically seeing as I don't have the time nor inclination to refute any more of your fallacious sycophantic dribble (work for AFACT perhaps? or even MRG?) all i can say is
Piss off, you contribute nothing and are about as useful as tits on a bull, come back when you grow up and are at least coherent. Either that or stop posting whilst your pissed!
[ link to this | view in chronology ]
Re: Re: The technology "made me do it" !!!
Oh and you stating that you (or anyone) could use the defense of insanity (mental incapax) in a civil court (or even for a traffic fine) shows how much you just don't understand about the Australian Legal system either.
[ link to this | view in chronology ]
Re: Re: The technology "made me do it" !!!
I also performed alot of consulting work at ANSTO with a private R&D company and with the ANU.
you really I am not interested at all in what you may or may not have done, or that it provided you with any more authority than anyone else to comment in an open forum.
[ link to this | view in chronology ]
Re: Re: Re: The technology "made me do it" !!!
I consult to a fair amount of Federal and State based departments on both IT Security, Digital Forensics and even get asked about IP situations and my opinion by Main Stream Media orgs , I even get quoted correctly sometimes too.. I know shock horror! as well as being an Aircraft Avionics Engineer (Qantas) before I sidetracked into the insane world of ITC and Law... oh and I play a fairly good game of solitaire in my spare time too.
But as you state and I agree it doesn't mean diddly squat when on a public forum. Though when talking about legalities to do with actual laws and not what you think the laws/statutes are or should be, it at least is a good idea to actually know what you are talking about and be able to comprehensibly rebuff critical arguments (or downright dumb statements)
So either acknowledge in your posts that you have no clue about IP laws and are only guessing and stating your personal opinion, or stick with what you know and give us a nice treatise on the wonderful world of Engineering with smatterings of nuclear physics(?) and how Australia is one of the best innovative and inventive countries when it comes to Engineering and the Sciences.
Though I have a suspicion that the persona you portray here is not how you are really like, they don't allow fools to work for ADFA, nor ANSTO. You're Intelligent Darryl, show it and use it to contribute , criticise, and logically debate posts. Otherwise it just becomes a slanging match of egos and I get enough of that every time I visit that building with the huge flag on the hill in Canberra. Hey and when America closes its isolationist borders on the Net soon (with their strange new laws) and with Europe imploding, we will be the last bastion of sanity left. HA..
Hope you had a good weekend. Mine? My starter Motor blew up.. Thank Gawd for the NRMA ;)
[ link to this | view in chronology ]
Re: The technology "made me do it" !!!
[ link to this | view in chronology ]
Re: Re: The technology "made me do it" !!!
Total believe that everything Masnick says is the word of GOD ?
The ability to put aside reality for Masnicks alternative reality ?
Your ability to leave all logic and reason behind when you read the dribble Masnick rants about ?
The willingness to disregard the law if you feel you are capable of breaking it.
If so you must be well qualified!!!!!
[ link to this | view in chronology ]
Re: Re: Re: The technology "made me do it" !!!
Because that would explain A LOT.
[ link to this | view in chronology ]
Re: Re: Re: Re: The technology "made me do it" !!!
But, yeah, I have to agree that the writing styles (lack of?) are similar.
[ link to this | view in chronology ]
Re: The technology "made me do it" !!!
it's Darrylrhea again!
[ link to this | view in chronology ]
Re: The technology "made me do it" !!!
[ link to this | view in chronology ]
Re: Re: The technology "made me do it" !!!
[ link to this | view in chronology ]
Re: Re: The technology "made me do it" !!!
house
house
a. A structure serving as a dwelling for one or more persons, especially for a family.
b. A household or family.
you OK now ???
Do you need to learn your left from right ?
[ link to this | view in chronology ]
Re: Re: Re: The technology "made me do it" !!!
[ link to this | view in chronology ]
Re: Re: Re: Re: The technology "made me do it" !!!
*shrug*
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: The technology "made me do it" !!!
I don't know if Darryl's necessarily Australian. I know I wouldn't claim him if he was.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Here is a GUN - it has a simple "point and click" interface.
Damn shame Masnick is so fixated on a single line at the top, (probably not even put there by the Author).
But if you read the actual ARITICLE you will find it most interesting and informative.
It clearly says that "technology" tends to work TOGETHER, and not in competition with each other (as Masnick would have you belive).
The article basically (and correctly) states IT's NOT THE TECHNOLOGY, but the APPLICATION and USE of that technology...
Mike still believes in the "field of dreams" dream, "If we build it they will come"
If I can do something, I MUST DO THAT THING..
Masnick are you technically capable of shooting yourself ?
After all, a gun is a simple "point and click" interface...
[ link to this | view in chronology ]
Re: Here is a GUN - it has a simple "point and click" interface.
Oh. Nothing.
[ link to this | view in chronology ]
Re: Here is a GUN - it has a simple "point and click" interface.
[ link to this | view in chronology ]
Re: Here is a GUN - it has a simple "point and click" interface.
[ link to this | view in chronology ]
Re: Here is a GUN - it has a simple "point and click" interface.
[ link to this | view in chronology ]
Re: Re: Here is a GUN - it has a simple "point and click" interface.
It's also years old, and their main page states you are welcome to link to any content, as long as you do not modify the work..
Normal copyright, just like Techdirt
[ link to this | view in chronology ]
But he's an expert in "electronic publishing"
"methods of high quality electronic publishing".
For all I know, he could be. I'm not -- I just publish op-eds and novels -- so I have no way of knowing. lol
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Probably a nod to the publisher
It's silly & unenforceable, but would make a little bit of sense from the point of view of the author trying to satisfy his publisher while posting his work.
Here's an example from another page,
"Copyright © 2005-present by T. Matthew Ciolek. This Web page may be linked to any other Web pages. Contents may not be altered. Unauthorised use or electronic dissemination is prohibited by applicable laws. Please contact the appropriate section maintainer for permission to re-use any material."
[ link to this | view in chronology ]
Copyright is whatever you want it to be
[ link to this | view in chronology ]
Re: Copyright is whatever you want it to be
[ link to this | view in chronology ]
Re: Re: Copyright is whatever you want it to be
That would explain their repeated attacks on 12-year-olds and computer nerds...
[ link to this | view in chronology ]
heres my content, I dare you to link to it.
BTW,
if linking is illegal for this page, why does the copyright holder request Google to not index (thru DMCA takedown)? Not knowing how to use the 'no index' codes in HTML. Failure to understand how indexing works? or they havent gotten beyond year 1 understanding of the Internet? (just like the courts).. and yes, capital I in Internet is Intentional. I wish I had a Ph.D., my engineering degree and 20 years of sucessfull design experience (but poor mastery of spelling) seems so minor now. If I could only get royalties on the things I have built, but you are now using.
[ link to this | view in chronology ]
From their main page:
URL http://www.ciolek.com
[ link to this | view in chronology ]
Isn't it funny...
[ link to this | view in chronology ]
REs
[ link to this | view in chronology ]
I see lots of analogy to GPL, wrong analogy.
An html link is like a card in the card catalog at the library.
The card tells me where to find the resource I am looking for.
Same situation if I use the libraries search feature, the computer tells me where to find the resource.
In both cases at the library there are links to resources and the links are not copyrightable nor can publishers of the resources prevent people from making these links.
Same applies to html links.
It is simply a reference to a resource.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
2005?
To put things into perspective, this was also the period when there was a whole debate regarding the legality of a browsers cache
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Trolly troll
"This site may be freely linked from other web pages world-wide."
Furthermore the site has a notice "Web sites around the world that link to www.ciolek.com." http://siteexplorer.search.yahoo.com/au/search?p=www.ciolek.com&bwm=i&bwmo=d&bwmf=u
T rololololol
[ link to this | view in chronology ]
Basically, when you view a web page, you make a copy. That's normally not infringement for a number of reasons, including that you probably have an implied license from the author (if they are the one putting it online) to make such a copy, because that's the only way to view the work and presumably that's why they put it online in the first place.
But, if the author explicitly states that he doesn't want a work to be viewed in a particular manner (i.e., by linking from a third party), then the implied license argument goes away.
Thus, if you know the author doesn't want you to link to his web page, and you do it anyway, you are arguably encouraging people to make copies in an unauthorized manner, which could subject you to liability for inducing infringement or contributory infringement.
Maybe none of that applies here, since someone else suggested his website has language stating that it *is* ok to link there.
But at any rate, it's not crystal clear that linking is *never* infringement (or, at least, contributory infringement or inducement).
[ link to this | view in chronology ]
Re:
How you got to that web page doesn't change the mechanism, purpose, or nature of the copying your browser does in order for you to view the page. Whether you type in the URL manually, link from the same web site, or from some 3rd-party site only changes the referrer, which has no bearing on the copying, and so has no bearing on the implied license to copy. Linking is not one of the exclusive rights defined by copyright law, either.
[ link to this | view in chronology ]
Re: Re:
That much is certainly true.
However, I'm not sure if the manner in which you get to the page is completely irrelevant to whether your viewing of the page is licensed.
Basically, you can define the terms of your license however you want. If you say "you can copy my work as long as you do three spins and hop on one leg for 30 seconds first," then copying of the work without meeting those conditions is not authorized.
It's true that the explicit terms refer to the linker, not the person following the link, but I think it's arguable that there is no implication your copying is authorized if you're doing so by following a clearly unauthorized method.
There may be a fair use argument that is unrelated to the license issue, of course.
Anyway, I just want to make sure that people aren't misled into thinking this issue is as black and white as the article makes it out to be.
[ link to this | view in chronology ]
Re: Re: Re:
It's true that the explicit terms refer to the linker, not the person following the link, but I think it's arguable that there is no implication your copying is authorized if you're doing so by following a clearly unauthorized method.
But you're not. The method of copying - which is what is at issue - is exactly the same. That's why I mentioned that linking isn't one of the exclusive rights. This is the same reason why it's fradulent for record labels to claim that you're not allowed to loan your CD to someone. Copyright law simply doesn't enable them to prohibit that. Same with linking: there's nothing in the law that enables them to restrict linking behavior, and there's nothing about the copying behavior that differs between the two scenarios of "authorized" and "unauthorized" link following.
[ link to this | view in chronology ]
Re: Re: Re: Re:
The difference between the CD analogy and the website scenario is that the author *does* have the right to prohibit copying, which happens when you visit the website.
So, if the author says "you can't visit my website unless you first (a) quack like a duck, (b) eat a pound of cherries, and (c) dig a 3'x'3'x3' hole," then it doesn't matter whether all those conditions are at all related to copyright law, your visiting of the website constitutes unauthorized copying if you don't fulfill those conditions.
In this case, the author is saying "you can't link to my website." So, I think there is at least an argument that any supposed implied authorization to visit his website does not extend to someone who followed an unauthorized link to get there.
I'm not saying it's clear cut, but since copyright law (U.S. copyright law, anyway) has essentially said that visiting a website constitutes a prima facie case of copyright infringement, you're playing with gray areas to begin with (implied license, fair use).
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
That could be true if it's possible to make an implied license conditional like that. I don't really know enough about implied licenses to say. The Wikipedia entry indicates there are some circumstances where an implied license exists even if the licensor is unwilling to grant it. This would seem to me a good candidate for such a scenario.
I'm not saying it's clear cut, but since copyright law (U.S. copyright law, anyway) has essentially said that visiting a website constitutes a prima facie case of copyright infringement,
I was under the impression it was the exact opposite, that the transient copy the browser makes has been ruled not infringement. I couldn't find a reference either way though, other than a court case in the UK. Do you have any information about it?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
http://cyber.law.harvard.edu/people/tfisher/IP/2007%20Perfect%2010%20Abridged.pdf
However , since fair use is a fact-specific inquiry, that doesn't necessarily mean that *all* temporary copies of internet pages are fair uses.
[ link to this | view in chronology ]
Deep linking, copyright, and "terms of use" agreements
In addition to copyright, there may be the issue of "terms of use" agreements. In particular, a "clickwrap" agreement where an "I Agree" button is presented next to a viewable copy of the agreement may be more likely to be enforceable than a "browserwrap" agreement where a link to a "terms of use" agreement is merely included among the other content on the site. (When a "terms of use" agreement includes provisions along the line of "You may use this site only for your personal and non-commercial use," the question comes up as to how that would affect a party who is doing a critical and public review about the site...)
[ link to this | view in chronology ]
Re: Deep linking, copyright, and "terms of use" agreements
[ link to this | view in chronology ]