<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
<title>Techdirt. Stories filed under &quot;copy&quot;</title>
<description>Easily digestible tech news...</description>
<link>http://www.techdirt.com/</link>
<language>en-us</language>
<image><title>Techdirt. Stories filed under &quot;copy&quot;</title><url>http://www.techdirt.com/images/td-88x31.gif</url><link>http://www.techdirt.com/</link></image>
<item>
<pubDate>Thu, 22 Mar 2012 12:08:53 PDT</pubDate>
<title>How Much Of Today's Copyright Mess Is Due To Bad Definitions Of The Word Copy?</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20120315/22541318119/how-much-todays-copyright-mess-is-due-to-bad-definitions-word-copy.shtml</link>
<guid>http://www.techdirt.com/articles/20120315/22541318119/how-much-todays-copyright-mess-is-due-to-bad-definitions-word-copy.shtml</guid>
<description><![CDATA[ The Guardian has up a short excerpt from William Patry's recent book, <a href="http://www.oup.com/us/catalog/general/subject/Law/IntellectualProperty/IntellectualProperty/?view=usa&#038;ci=9780199760091" target="_blank"><i>How to Fix Copyright</i></a>, which is a really enjoyable read.  I don't necessarily agree with everything in there, but almost all of it is thought provoking and relevant to the discussions we have around here.  The excerpt is actually from the beginning of the book, it highlights how much of the confusion over today's copyright law might be because people have been confused over what definition of "copy" we're using.  As he notes, "copy" can be both a verb and a noun -- and <i>at first</i> copyright appeared to be about the noun version, but relatively early on, <a href="http://www.guardian.co.uk/law/2012/mar/13/how-to-fix-copyright-extract" target="_blank">people redefined it to cover both the verb and the noun</a>, but people aren't always clear which one they really mean:
<blockquote><i>
The word "copy" has two meanings. As a verb, "to copy" means reproducing content from one work into either another work (we say one song was "copied" from another song). It also means that copying into another form (you "copy" your CD onto your iPod). The verb of "copy" is what we mean by the exclusive right to reproduce a work. "Reproduce" is a synonym version of the verb to copy. The noun version of "copy" refers to a physical object, a CD or the mp3 file on your iPod that contains the intangible work (the song or the performance). When I say I own a CD "copy" of a work, I am referring to the noun.
<br /><br />
The original use of "copy" was in the noun sense. In England, book publishers spoke of owning rights in their "copies," meaning the printed production. The 1710 Statute of Anne, in its title, also spoke of "vesting the copies of printed books in authors or purchasers of such copies...." The right granted - the verb - was the right to "print" those copies. The right to print later became the right to reproduce, with reproduce being regarded as a synonym for the verb to copy. The term "copyright," though ambiguous, referred to either the noun or the verb. Most copyright acts, including the US Copyright Act, combine both the verb and noun versions: the right granted in 17 USC 106(1) is the right to "reproduce the work in copies."
</i></blockquote>
But these days, thanks to these misinterpretations, we get bizarre thinking from copyright maximalists:
<blockquote><i>
Unfortunately, through mistaken interpretations of the noun "copy," the reproduction right has been wildly expanded in many countries, particularly the United States, to include transitory acts such as buffering, caching, or non-consumable versions that are necessitated by the automatic operation of computers or other digital technologies. None of these transitory acts has an independent economic value; that is, they do not harm copyright owners' markets. For example, in order to ensure that the streaming of a video is not interrupted by breaks in the transmissions, websites copy ("buffer") small parts of the video so that missing pieces can be filled during the interruption. Browsers make caches of websites that you just visited in case you hit the "back" button and want to revisit a site you just left. Other caches help with latency (response) time, and managing network traffic. Other times, a cache is made in case websites are inadvertently deleted. To consider buffering or caching to be infringing "copies" is using an eighteenth-century concept to defeat necessary twenty-first-century technologies, the only purpose of which is to increase performance. Where "copies" are made as a necessary adjunct for other legitimate purposes, no liability should exist. Amending the definition of "copy" in either the noun or verb version is an easy fix that would go far in assisting musical licensing and in removing the specter of mass, unintentional copying.
</i></blockquote>
The piece goes on to note that this version of "copying" under copyright law makes all sorts of new services -- those based around access rather than ownership -- a huge minefield of potential copyright violations.  And it's all made that much worse when you add in the ridiculous <a href="http://www.techdirt.com/blog/innovation/articles/20120313/11281118092/why-anti-circumvention-laws-are-evil-hollywood-gets-to-veto-dvd-jukebox-despite-complete-lack-infringement.shtml">anti-circumvention</a> clauses, because that effectively gives the entertainment industry a veto on technology, despite having nothing to do with violating copyright law.
<blockquote><i>
The DMCA and other digital lock laws are prime examples of our march backwards, of how our laws are used to thwart innovation and creativity. The DMCA is the reason you can't load lawfully purchased copies of your DVDs into your iPod, why you can't transfer copies of many lawfully purchased works from one electronic device to another, why DVDs bought in one country may not work in another, something that greatly embarrassed (or should have) President Obama when he gave then&#8211;United Kingdom prime minister Gordon Brown a set of DVDs of American movies, which couldn't be lawfully played on Brown's DVD player.
<br /><br />
The DMCA will permit copyright owners to control how many times you can read or watch a copyrighted work. In the DMCA world, both consumers and technology are treated as the enemy.
</i></blockquote>
And, as he notes, this is unfortunate not just for technology companies -- but for consumers <i>and</i> the artists and content creators they want to support:
<blockquote><i>
This unfortunate approach ignores that consumer expectations are greatly influenced by technologies. It is new technologies, not new works, that lead to new consumer expectations and therefore new sources of profits for authors. The Sony Walkman led to an explosion of new sales of audio cassettes. The same was true of the introduction of the CD, where for most of its product life, more money was made from consumers re-buying existing albums than from buying new ones.
<br /><br />
But for new technologies, the copyright industries and authors would have starved long ago, since they have played no role, creatively or financially, in the development and introduction of the technologies that enable them to make money. Not a single penny was contributed by the music industry to the creation, manufacture or marketing of iTunes, the iPod, or the iPad. Not a single penny was contributed by the copyright industries to the development of the internet or to any search engine even though the copyright industries could not exist without either. New technologies provide new ways to satisfy new consumer demand and to thereby make healthy profi ts. You would never know that from the medieval mentality of moat building represented by the DMCA and copyright industries' approach to most new technologies, an approach that has failed to grasp the simple point, proved over and over again, that new technologies create new opportunities.
</i></blockquote>
There's a lot more in the article that's worth reading, and even more in the full book, which I recommend highly.<br /><br /><a href="http://www.techdirt.com/articles/20120315/22541318119/how-much-todays-copyright-mess-is-due-to-bad-definitions-word-copy.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20120315/22541318119/how-much-todays-copyright-mess-is-due-to-bad-definitions-word-copy.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20120315/22541318119/how-much-todays-copyright-mess-is-due-to-bad-definitions-word-copy.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>messy-messy</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20120315/22541318119</wfw:commentRss>
</item>
<item>
<pubDate>Thu, 3 Jun 2010 11:10:26 PDT</pubDate>
<title>Messing With Copy/Paste Could Present Security Issues</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20100601/0047399633.shtml</link>
<guid>http://www.techdirt.com/articles/20100601/0047399633.shtml</guid>
<description><![CDATA[ John Gruber recently highlighted one of the more annoying things I've seen on multiple news websites lately: <a href="http://daringfireball.net/2010/05/tynt_copy_paste_jerks" target="_blank">attempts to muck with basic copy &#038; paste features</a>.  I've noticed it on Wired.com and SFGate.com among others.  Gruber points out that it's also happening on TechCrunch and The New Yorker's website.  From a user's standpoint, what happens is that when you copy some text, and then paste it somewhere else, through some javascript shenanigans, it appends a bit of <b>extra</b> text that you did not copy, usually saying something like "read more:" with a URL linking back to the original story.
<br /><br />
As someone who does a fair bit of copying and pasting in writing this blog, I agree with Gruber that this is a bit of a nuisance.  It's not a <i>hugely</i> annoying thing, but it is annoying.  If I'm copying and pasting from your website, I know what your website is, and I am already planning to link back to it.  Adding that superfluous text is just annoying and basically forcing my computer to do something I did not ask it to do.
<br /><br />
Gruber tracked down the source of this annoyance: a company called Tynt, that not only enables this functionality for a bunch of sites that probably don't realize how annoying it is, but also <i>tracks what you copy</i> by sending that info back to its server.  That's a bit creepy, frankly.  Of course, since it's javascript, it's easy enough to block for those who know how to do that sort of thing.  Still, Gruber's analysis of this makes sense:
<blockquote><i>
It's a bunch of user-hostile SEO bullshit.
<br /><br />
Everyone knows how copy and paste works. You select text. You copy. When you paste, what you get is exactly what you selected. The core product of the "copy/paste company" is a service that breaks copy and paste.
<br /><br />
The pitch from Tynt to publishers is that their clipboard jiggery-pokery allows publishers to track where text copied from their website is being used, on the assumption that whoever is pasting the text is leaving the Tynt-inserted attribution URL, with its gibberish-looking tracking ID. This is, I believe, a dubious assumption. Who, when they paste such text and find this "Read more:" attribution line appended, doesn't just delete it (and wonder how it got there)?
</i></blockquote>
However, it may be even worse than that.  <a href="http://twitter.com/PrivacyLaw/status/15124683589" target="_blank">Michael Scott</a> points us to another analysis of this same issue, by Lance Cottrell, which highlights <a href="http://www.theprivacyblog.com/online-privacy/copy-paste-intercept-snoop/" target="_blank">how this breaking the basic copy/paste functionality may be a security risk as well</a>:
<blockquote><i>
Imagine a site with sample code which (when copied) inserted some damaging code in to the middle of a large block.
<br /><br />
I am worried that this capability exists at all within browsers. It seems like a major security vulnerability to me.
</i></blockquote>
Bad things happen when you break basic functionality to shove in fun marketing tricks and spy tactics.<br /><br /><a href="http://www.techdirt.com/articles/20100601/0047399633.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20100601/0047399633.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20100601/0047399633.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>just-let-copy-and-paste-work</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20100601/0047399633</wfw:commentRss>
</item>
<item>
<pubDate>Fri, 22 Feb 2008 18:12:03 PST</pubDate>
<title>Your Dating Profile Not Exciting Enough?  Just Borrow Someone Else's</title>
<dc:creator>Dennis Yang</dc:creator>
<link>http://www.techdirt.com/articles/20080221/133302315.shtml</link>
<guid>http://www.techdirt.com/articles/20080221/133302315.shtml</guid>
<description><![CDATA[ Now that online dating has become commonplace, would-be suitors are having a hard time making themselves seem interesting in an increasingly large dating pool.  So, what to do if your own interests and achievements are boring and average?  Well, <a href="http://online.wsj.com/public/article/SB120303234117369959.html?mod=blog">just borrow the good bits of the exciting profiles that you find, and add them to your own</a>.  Apparently, these acts of profile plagiarism are fairly commonplace now amongst the online dating set.  When people find well-written, exciting descriptions, they grab them for their own profiles.  Unfortunately for the daters, eventually, a real-world meeting delivers a product that the marketing has misrepresented, and disappointment usually results.  Although in some cases, it's possible to track down the "original" author, most origins are fairly difficult to trace -- surely more than one person enjoys "long walks on the beach."<br /><br /><a href="http://www.techdirt.com/articles/20080221/133302315.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20080221/133302315.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20080221/133302315.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>nobody-knows-you're-a-dog</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20080221/133302315</wfw:commentRss>
</item>
</channel>
</rss>