Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling Take Control ebooks.

 

Edit Remote Files in Your Favorite Utility with Fetch

If you use the Fetch FTP client and want to, for instance, edit remote .html files with one application but .css files with another, you can set this up easily: In Fetch, select a .html file and click the Get Info button on the toolbar. In the Get Info window, in the Transfer Option section, choose your desired program from the "Edit files like this with" pop-up menu. Repeat the procedure for a .css file, and you're ready to go!

Visit Fetch Softworks

 

 

Recent TidBITS Talk Discussions
 
 

Double Plus Ungoods: Amazon Unpublishes Orwell

Amazon ripped two George Orwell books, their hearts still beating, from the Kindles of its customers. Reaction to the move provoked a firestorm of opinion related to ownership and permission, and Amazon swore off deleting customers' content from the Kindle again. However, the firm also found itself in an awkward position, one that most reports seem to have ignored or glossed over.

The blast erupted from Amazon deleting two works - in a stunning bit of poetic reality, "Nineteen Eighty-Four" and "Animal Farm" - that it says a third-party Kindle content publisher lacked the rights to offer for sale. The publisher, MobileReference, sells formatted versions of public-domain works, among other titles.

Amazon certainly made the wrong move by deleting the books remotely without advance warning, taking along with them any associated bookmarks and notes. There was no question that customers purchased the books in good faith. However, the company was also certainly required to resolve a situation in which it was violating copyright.

It's worth looking at how this situation - a somewhat unusual case - arose, along with what Amazon has previously said about the rights it gives Kindle subscribers, and what this bodes for the future.


In the Public Good -- George Orwell died in 1950, which presents a spot of difficulty related to his copyright. In some countries, his works are in the public domain, but not in the United States. Generally uniform international copyright law was adopted in the 1970s, and modified in loose harmony since then.

Current U.S. law puts works published before 1923 in stark relief: they're all in the public domain. Added to this is the set of works published between 1923 and 1950, which were initially allowed a single 28-year term, and later offered a renewal term of the same duration. Works in that period that weren't renewed are now in the public domain.

All other works have been swept into a new regime that provides a super-long extension. And all works created since 1977 are covered for an author's life plus 70 years. (For a full rundown, see the section, "The Variety of Works under Discussion," in "Authors and Publishers Settle with Google Book Search," 2008-10-29, and also Peter Hirtle's "Copyright and the Public Domain in the United States.")

Orwell's works were published before his death in the United Kingdom, and a search at the U.S. Copyright Office shows that "Animal Farm" was first registered here in 1950. Ostensibly, all these valuable works had their terms renewed, too. (Initial registration isn't required, but establishes ownership and triples damages in successful lawsuits; renewal was required, however.)

Any work that was published with U.S. formalities (such as copyright notice and renewal) had its copyright extension revised to be 95 years from the initial copyright registration. "Animal Farm" is thus under copyright protection in the United States until 2040; "Nineteen Eighty-Four" is protected until 2044.

In Australia, however, changes in copyright law vary for authors who died before and after 1954, and don't take into account a work's publication date. Australia extends copyright to 50 years after death for authors who died in 1954 or earlier, and to 70 years after death for authors who passed thereafter. All of Orwell's works are available online at no cost at various Australian sites. (Project Gutenberg in Australia has a nice summary of that country's rights.)

While MobileReference hasn't yet commented publicly, the firm seems to traffic entirely in public domain works and thinly assembled reference documents (biographies of all U.S. presidents, for instance). It's likely the company made a mistake in including the works in the United States.


What Rights We Mortals Have -- When we buy a physical book in the United States, we have the right to possess it forever, pass it on to heirs as part of an estate, burn or deface it, loan it and expect its return, donate it, and resell it. The new owner has the same set of rights. (Notably, those rights weren't always crystal clear; the first-sale doctrine that allows resale, for instance, has been litigated, but upheld.)

When we purchase digital media, whether music, video, or books, we are nearly always purchasing a license, not obtaining ownership. We typically, but not always, cannot resell what we buy, because we're obtaining a perfect digital copy. That implies that a publisher or rights holder can't be sure that we've deleted a work when we pass it on, even though there are ways to ensure that in systems that restrict the right to pass works on.

Apple's iTunes Store agreement is pretty typical, in that it says we receive specific non-commercial, personal rights to playback limited by digital rights management technology. For iTunes Plus music, which is DRM-free and all that Apple now offers for music, you're asked to self-limit what you do.

But Apple's agreement has a nifty little statement in it that has long made some people wary of buying anything from the company - despite the billions of songs sold so far:

"Apple and its licensors reserve the right to change, suspend, remove, or disable access to any Products, content, or other materials comprising a part of the Service at any time without notice."

Which means: "It may seem like you bought it and it's yours, but we can remove stuff from your phone, computer, or iPod, and we don't even have to tell you why or alert you ahead of time."

DRM annoys people because of these kinds of statements. DRM has a single legitimate purpose: deterring the unpaid spread of those perfect digital copies. Its illegitimate purposes are legion, including restricting our legal rights - in the United States and elsewhere - to shift content around for personal use, among a family or on hardware we own. (There are arguments about what "personal use" means. I was once involved in a lawsuit on the side of ReplayTV to defend personal use: Newmark v. Turner.)

The RIAA and MPAA and other organizations want to allow the fewest possible rights in order to ensure that the same work is purchased the most possible times by the same people. If we could simply copy our DVDs to standard computer formats, the studios would have more trouble convincing us to buy the same movies again for Blu-ray, as we did with the jump from VHS to DVD.

DRM also lets device makers and application developers hold a sword over your head about the usage of the code and gear they provide. That's the crux of Amazon's Orwell debacle.

Amazon's contract is much fairer for the purchaser than Apple's for iTunes and similar licenses for digital "sales" of music and visual media. Amazon says:

"Amazon grants you the non-exclusive right to keep a permanent copy of the applicable Digital Content and to view, use, and display such Digital Content an unlimited number of times, solely on the Device or as authorized by Amazon as part of the Service and solely for your personal, non-commercial use."

Translated, this means that you're gaining something akin to ownership, in that the digital copy is yours to use forever. But it then notes, of course, that you don't really own it:

"Unless specifically indicated otherwise, you may not sell, rent, lease, distribute, broadcast, sublicense or otherwise assign any rights to the Digital Content or any portion of it to any third party..."

Neither of the terms above say explicitly that Amazon can reach into your Kindle library (a set of book purchase records stored on its servers) or into your device and remove a book or other item you have purchased (or, more appropriately, licensed).

But there's a catch:

"Digital Content will be deemed licensed to you by Amazon under this Agreement unless otherwise expressly provided by Amazon."

That means "We licensed you something and now have decided it is no longer licensed to you for whatever reason." That's legitimate under the contract.

In this case, Amazon was told that it was providing rights to a work that it didn't have permission to provide. Though Amazon agreed that it was in the wrong to have sold these copies of "Nineteen Eighty-Four" and "Animal Farm," its next move was a mistake, and one the company now admits.


What Amazon Wrought -- Amazon and Apple use different approaches to where your digital media purchases live. The iTunes Store agreement says you get to download stuff once and once only. Don't lose your data, and it's your problem to store it and back it up.

In contrast, Amazon built an infrastructure that supports many devices from different makers with different storage capabilities, coupled with streaming video. So Amazon creates for you an online library from which you can stream or download. If you delete purchased content or lose a device, you can re-download your content again. (Amazon does impose a limit on the number of devices to which content can be downloaded at any given time. That number is explicit for video; audio is DRM-free and thus not tracked; and books appear to have something like a six-device limit that's squishy and not mentioned in the company's terms of service.)

In the case of the two Orwell books, once Amazon agreed with the legitimate rights holder that MobileReference didn't have permission to distribute the works, Amazon had to make some kind of move.

The company clearly should have deleted the two Orwell books from its library and from all user online libraries - which it did - effectively preventing new purchases and new downloads. It also should have refunded any fees paid by customers for the books, which it also did. And it should have notified users; again, Amazon did so.

But then it seems that someone at Amazon got too excited with what's called "remote self-help technology," which allows a firm to reach out into your computer and other devices to disable hardware, software, or content. The late Ed Foster, a terrific writer and advocate for tech users, spent years inveighing against a modification to the U.S. commercial code used by most states that would allow software makers to place kill switches in code that users couldn't disable, appeal against the use of, or have reasonable grounds to prevent. Self-help rightly bothers us. (Ed won in the end.)

Because Amazon, unlike Apple, didn't specifically reserve the right of self-help, its remote deletion may both have broken laws and rendered Amazon subject to a lawsuit, although damages would likely be slight. It's understandable that Amazon wanted to remove all infringing works from all devices, but Kindles aren't per se under Amazon's control, and that's even more true of the Kindle for iPhone software.

One hopes the decision was made by someone who simply didn't understand the implications, and how much a response this action would provoke. I can't imagine that anyone in Amazon would want to pull the kill switch on "Nineteen Eighty-Four" - of all books - in this manner. Amazon was trying to avoid liability for distributing unauthorized copies of the two works, and thus took all possible actions, instead of reaching out to its readers.

Had I been forced to make this decision, I might have gone so far as to have each purchaser called directly to explain the situation - only hundreds of people were involved. I certainly would have tried to offer a substitute licensed copy, and probably would even have sent print editions of the books along with a gift certificate. And I would have asked users either to let Amazon delete the book or relied on the user to delete the title in some verifiable fashion.

That might have cost a few tens of thousands of dollars, versus the equivalent of millions of dollars in bad publicity and lost Kindle sales as people associate Amazon with the memory hole. The company, chastened in a way it rarely shows, says it won't delete books this way again.

Amazon's actions have been described as ironic, which is incorrect. Irony describes an event that is inconsonant with and contrary to the expected order of things, or words that deny their own reality. In "Nineteen Eighty-Four," slogans like "War is peace" are ironic.

No, Amazon acted with a perfect lack of irony, completely in accord with elements of "Nineteen Eighty-Four," however prosaically it aped Orwell's words. A strong echo came to me from Part 2, Chapter 10 of "Nineteen Eighty-Four," when a steely voice recites to the book's protagonist, Winston Smith, "Here comes a candle to light you to bed. And here comes a chopper to chop off your head!"

Is it any wonder self-help technology freaks people out?

 

SYNC YOUR PHONE with The Missing Sync: Sync your calendar,
address book, music, photos and much more between your phone
and Mac. Supports ANDROID, BLACKBERRY, PALM PRE and many
other phones. <http://www.markspace.com/bits>
 

Comments about Double Plus Ungoods: Amazon Unpublishes Orwell

dave holle 22009-07-19 21:55
Excellent article. Thanks.
Edward Walters2009-07-20 09:51
Thanks for the summary of different cases. This is a great short-form resource for those of us who deal with these issues.
Sensei J. Richard Kirkham B.Sc.2009-07-20 10:01
1984 all over again. Time to boycott Big Brother - Amazon
http://KirkhamsEbooks.com
An excellent reference for copyright information is the Internet Archive: http://www.archive.org/about/about.php#5

DRM is Freedom #minitrue
Detailed but easily understood. Thanks for the excellent article.
What I'd really like to know is how an earth any novel can have copyright for 70 years after an author's death?

Isn't JK Rowling rich enough already without the monopoly really having to continue ?
Glenn Fleishman2009-07-28 09:04
Lots of people have the same take on it. The Constitution enshrines some intellectual property protection that's supposed to balance both the value of a creator exploiting his or her or their work, and the fact that the entire society is enhanced by creativity that becomes the property of the whole.
"allow software makers to place kill switches in code"

This might be illegal but golly is it useful to get recalcitrant customers to pay up for software developments after having waited 6 months for payment. I once had a customer who hadn't paid and I didn't have much hope so I delivered them an "update". One week later there was a "bug". One day after that I had a check and the "bug" was fixed. Don't misunderstand me the program I delivered originally worked exactly to specification and 4 people were working on it every day. The customer did figure out what had happended, threatened me with litigation but when I pointed out that he would still owe me the money he decided to become honest.
Glenn Fleishman2009-07-28 09:03
Not to put too fine a point on it, but you engaged in what was likely both criminally prosecutable and civilly liable offenses. Even with contracts in place that allow remote disabling of software, those terms typically aren't enforceable. Because you did this slowly, without warning, and with the intent of (at least as you describe) disrupting business, had he called the police or (if across state lines) the FBI, you might have faced a jail term of 1 to 10 years.
The proper way to handle this is to use good contracts and civil courts, or to collect substantial fees before final delivery.
Or, you can use a serial scheme that requires ongoing payment to get the next serial number to renew a subscription.

In fact, in your shoes, I might have added an "activation code" that would only have been provided when payment was received and would have limited the system to minimal transactions.

Don't go to jail over something like this.
I would never do this in the US or the UK. I know that the law is pretty strict even if the motivation might evoke some sympathy.
I did this in France where the law about this is far more foggy. What I now do is introduce the "bug" right at the beginning therefore thay wouldn't realise that it was designed to make them pay up. When the client does pay they get an "upgrade". If they haven't paid when the bug happens I agree to come in immediately to fix it and remind them at the same time that they still owe me money. Having said that it has only happened twice in 10 years.
The real gem was the 1st client saying that I wasn't "customer oriented". As if anyone wants a non paying client...
Glenn Fleishman2009-07-28 13:40
That's an extremely immoral and fundamentally unethical act regardless of the country in which you operate.

I can understand not trusting that clients will pay as promised; that happens to everyone who receives any payment from someone else (employer or client or whatever).

However, most of us learn to work around that by refusing work where we think we won't get reliably paid; by using courts; by using shame.

I abhor the technique you're describing because it's dishonest.
It is dishonest, you're right. It is however designed to circumvent dishonest practices by clients : not to pay me when I've done the proper job as expected and to the best of my ability. No one has ever suffered through this (except the two clients who had no intention of paying me and therefore had to),
Refusing to work with some people is possible; courts, well they're expensive and time-consuming; shame : no way, these people have no shame.
Please don't assume that because I do this that for the rest I might be dishonest. I've been had a few times and I've just adopted a work-around. I might add that my debts to sub-contractors are paid immediately and I fail to understand why others can't behave the same way to me.