CARP Put to Death, but DMCA Is still Sleeping
“Did they say it was insane?”
That's what an FCC official said to me after I delivered the news that the Librarian of Congress had shot down the CARP (Copyright Arbitration and Royalty Panel) Report's recommendations for internet radio. We're both at a computer/telecom industry conference. Among the several other people standing around hearing my report, huzzahs went up. CARP's mandate would have taken effect on May 22, 2002.
CARP was widely regarded, especially in internet radio circles, as a death sentence for the whole category. Instead the sword cut the other way.
Here's how the death sentence reads:
On May 21, 2002, the Librarian of Congress, based upon the recommendation of the Register of Copyrights, issued an Order rejecting the Panel's determination proposing rates and terms for these licenses. In such cases, the law provides that the Librarian shall issue his final determination within 30 days of his decision to reject the Panel's proposed rates and terms. The final determination is due on June 20, 2002.
And here is the Order, complete:
In the Matter of Digital Performance Right in Sound Recordings and Ephemeral Recordings
Docket No. 2000-9 CARP DTRA 1&2
On February 20, 2002, the Copyright Arbitration Royalty Panel (CARP) reported its determination to the Librarian of Congress in the above-captioned proceeding. In accordance with 17 U.S.C. 802(f), the Librarian is given 90 days from date of delivery of a CARP report to review the determination and issue a decision setting forth the final royalty fee and terms of payment. However, if the Librarian rejects the CARP's determination, section 802(f) provides an additional 30 days for the Librarian to render his final determination.
The Register of Copyrights recommends, and the Librarian agrees, that the CARP's determination must be rejected. A final decision will be issued no later than June 20, 2002.
DATED: May 21, 2002
Marybeth Peters, Register of Copyrights.
Thank you, Marybeth Peters.
Ironically, the CARP panel was convened by the Library of Congress. The panel wasted a large amount of energy and time in the course of recommending highly complex copyright obligations, including payments for performance rights, all intended to fulfill requirements of the Digital Millennium Copyright Act (DMCA).
This morning's announcement from the Librarian of Congress makes perfect sense, as the likely impact of the CARP's recommendation—the virtual shutdown of internet radio—would have been totally contrary to the legislative intent of establishing a statutory royalty rate in the first place!
One benefit of attending the Copyright Office's roundtable on recordkeeping requirements two weeks ago was the chance to see and hear Register of Copyrights Marybeth Peters and General Counsel David Carson and realize that they seem to have an excellent handle on the issues involved. The decision on an appropriate royalty rate seems to be in good hands.
The CARP report drew immediate and steady resistance from the moment it was published in February 2002. In “Webcasting Legally”, Jamie Zawinski ran down the list of station reporting obligations, prohibitive even for stations that have troubled to keep records of what they've played and when, such as the Linux-powered KPIG and Radio Paradise. Those stations, which have up to several thousand listeners at any given time, would have been bankrupted immediately by CARP's payment obligations. Here's the math of the matter, according to Internet News:
Here's how the 14/100 of a cent per performance royalty rate would translate for a webcaster with about 500 listeners per day: 500 listeners x .0014 dollars x 15 songs per hour x 24 hours = $250 per day or $90,000 per year, retroactive to 1998.
Here is some more background:
This CARP report may be dead, but the Digital Millennium Copyright Act remains in force, which means concerns about its implications are still quite alive.
We still need to deal with the differences between our default understanding of radio, and the DMCA's characterization of internet broadcasts. Instead of “stations” with “signals” that carry “programs”, the DMCA sees sources of streams that distribute “performances” (that's the key term), as if the radio were a stage in a performance hall. It presumes there is a business here and wants to charge rates for it. The big problem is that no business worthy of the noun has emerged in a state finished enough to even begin guiding regulation.
The CARP report struggled at length with the perceived need to describe a “willing seller” and a “willing buyer”. Terrestrial commercial radio has never had anything of the sort, at least between stations and listeners. Commercial radio's customers are advertisers, not listeners. With internet radio, on the other hand, listeners are in a perfect position to be customers and not just “consumers”. In some cases, such as Radio Paradise's, there is real income through PayPal contributions—up to thousands of dollars per month. But Radio Paradise is the exception. Most web stations essentially give the goods away just like terrestrial radio does, but potentially in a far more accountable way—and that's the rub.
It's clear now that advertising isn't going to sustain internet radio stations any more than it will sustain print publications on the Web. In fact, it's an open question how long advertising will remain a working source of revenue for terrestrial radio stations, especially if new technology makes the relationships between stations and listeners accountable, as TiVo is threatening to do for the relationships between commercial television and its viewers. What's at risk isn't the relationship between stations and listeners, which has always been weak (since listeners paid zero for the goods, their influence rounded to the same), but between stations and advertisers. When mute buttons get wired back to advertisers, the broadcast advertising game will be radically changed, if not killed outright. Broadcast advertising has always been inefficient, unaccountable and thick with unseen but very real waste. Once the accountability appears and the inefficiency and waste fully exposed, the only serious question is how much advertising goes away.
So pay-for-play is the only choice. It's not without precedent in terrestrial radio, since that's what has sustained noncommercial broadcasters for many years. Public broadcasting doesn't suffer that same split between customers and consumers that afflicts commercial broadcasting.
Commercial radio broadcasters might not be willing to look to the noncommercial model for guidance, but internet broadcasters don't have a threatened revenue model to discourage them.
What they need now is a chance to develop. Stations like Radio Paradise are pioneers, but it's too early to call them models for a whole new marketplace. That marketplace needs a chance to emerge and grow, which means now is the time to trust the Commons, not to regulate it away.
Between writing the last paragraph and this one I scarfed down a quick lunch in the informative company of Dave Burstein, Proprietor of DSL Prime and co-host of the Personal Computer Show on WBAI in New York. He gave me a high five when I told him the news about CARP. Then, for perspective on the issue, he offered this famous quote from A.J. Liebling: “Freedom of the press is guaranteed only to those who own one.”
Thanks to Marybeth Peters, thousands of internet broadcasters still enjoy their first amendment guarantees. We need to do everything we can to keep those guarantees safe.
Doc Searls (firstname.lastname@example.org) is senior editor of Linux Journal. His opinions are his own.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide