Luddite Redux: Don't Kill The Robots Just Because They Replace Some Jobs
from the first,-do-no-harm dept
Here are a couple points to ponder:
Fun fact #1: California prison guards are expensive.I'm sure the prisoners welcome their new robot overlords, but I bet the prison guards union doesn't. Or any other union for that matter. And they're not alone. Over the past few weeks, tech industry commentators spent slightly more time than usual wringing their hands over whether technology was killing jobs. I think this video captures the debate pretty well.
Fun fact #2: South Korea's getting robot prison guards.
This isn't a theoretical issue. Automation and efficiency have always threatened certain jobs and industries -- and one of the standard reactions is to somehow blame the technology itself and seek to hinder it, quite frequently by over-regulation. Of course, the extreme version of this is where the term "luddite" came from -- an organized effort to attack more efficient technology. Of course, that resulted in violence against the machines. More typical were overly burdensome regulations, such as "red flag laws," that said automobiles could only be driven if someone walked in front of them waving a red flag to "warn people" of the coming automobile. Supporters of this law, like supporters of secondary liability laws for robots, can and will claim that there are "legitimate safety reasons" for such laws and that the impact on holding back the innovation and extending the lifetime of obsolete jobs is just a mere side benefit. But like those red flag laws, applying secondary liability to robotics would significantly hinder a key area of economic growth.
Techdirt has covered the question of a secondary liablity safe harbor for robots before, and Ryan Calo's written a great paper about the legal issues coming out of the robotics arena, but an even more important (and specific) point is exactly why these safe harbors matter for job creation -- even as some continue to argue the other way (that such safe harbors will destroy jobs).
Technology has been replacing human labor since humans invented, well, technology. But while technology may get rid of inefficient jobs, it eventually creates replacements. To cite one commonly-used example, the switched telephone network put operators out of a job, but it created plentiful new jobs for telemarketers (and other businesses that relied upon the packet-switched phone network... including everything built on and around the internet today). The problem is that while it was obvious how many operators would be out of a job, it wasn't immediately clear how lucrative (or annoying) telemarketing could be, let alone the eventual transformation of the phone lines into a vast global information sharing network, and the hundreds of millions of new jobs created because of it.
Erik Brynjolfsson and Andrew McAfee examine this problem in detail in their book, which I recommend. But much of it boils down to this. Technology creates jobs, yet it's not obvious where the new jobs are, so we need bold, persistent experimentation to find them:
Parallel experimentation by millions of entrepreneurs is the best and fastest way to do that. As Thomas Edison once said when trying to find the right combination of materials for a working lightbulb: "I have not failed. I've just found 10,000 ways that won't work." Multiply that by 10 million entrepreneurs and you can begin to see the scale of the economy's innovation potential.This is especially important for robotics. It's obvious how robots make certain jobs obsolete -- e.g. driverless cars don't need drivers -- but it's less clear what new job opportunities they open up. We need to try different things.
Unfortunately, secondary liability creates problems for robot manufacturers who open up their products for experimentation. Ryan Calo explains this in more detail, but the basic problem is that, unlike computers, robots can easily cause physical harm. And under product liability law in most states, when there's physical harm to person or property, everyone involved in the manufacturing and distribution of that product is legally liable.
Ideally, we'd want something like a robot app store. But robot manufacturers would be unwilling to embrace commercial distribution of third-party apps if it increased their chances of being sued. There's evidence that Section 230's safe harbors (and, to some extent, the DMCA's safe harbors) play a key role in facilitating third-party content on the web. Absent a similar provision for robots, manufacturers are more likely to limit their liability by sticking to single-purpose robots or simply locking down key systems. That's fine, if we know exactly what we want our robots to do -- e.g. replace workers. But if we want robots to create jobs, it'd help to limit secondary liability for the robotics industry, open things up, and let widespread experiments happen freely.


Re: rangeCheck
Scratch that. Code is here: http://www.quora.com/Android-OS/What-were-the-actual-9-lines-of-code-that-Google-allegedly-copied-fr om-Java-for-Android
Yup, still real complicated
rangeCheck
Went looking for the code, not sure if this is it, but here's what I found at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5103956:
Yeah, that saved Google lots of time to copy.
Fair Use Serves Too Many Goals
I suppose future excerpts might address this, or maybe I should just buy the book ... but it seems that fair use is trying to do too many things at once.
There are lots of interests at stake when arguing for fair use. A handful off the top of my head:
* First Amendment rights to critique the original work
* A reluctance to impose penalties for "harmless" infringement
* A subsidy for favored uses like education
* A way for judges or other policymakers to fine-tune copyright and maximize the overall variety of works being produced
* A fallback for uses that sort of but don't quite fall within other copyright limitations like first sale or the inability to copyright facts
Trying to cram all of these uses into fair use might be why it's this vague balancing test that's so easily abused by well-lawyered interests. Maybe one way to "fix" copyright would be to split fair use up into multiple independent defenses.
Solutions
Product placement. Or some other way to display ads while the actual content is playing (kind of how YouTube ads work). Or, better yet, make your ads worth watching (e.g. like SuperBowl ads).
Re: This is the end of the discussion
Well, you could always try suing the government. If it's an ongoing violation, or if you're likely to have your rights violated in the near future, then you can sue the government to make it stop.
But if it's a one-and-done deal, then it's a lot harder. In the past, courts have awarded monetary damages to people who've had their 4th Amendment rights violated (see Bivens v. Six Unknown Federal Agents), but AFAIK, they've never done that for 1st and 5th Amendment claims. I suppose you could also argue that the website seizure was a "taking" without compensation and demand payment for the one year it was seized, although I'm not really up to snuff on takings law.
Re: Er ... wouldn't any app that redirected to Safari violate this?
For that matter, if you redirected to any website with ads, you would violate the policy. Because you could click on an ad which sends you a page you can buy stuff.
Er ... wouldn't any app that redirected to Safari violate this?
Because once you're in Safari, for whatever reason, you could always type in the URL to Amazon in the address bar. And then, you know, buy stuff.
Re: Re: Privatization
Agreed. I'd pay money for the mail equivalent of Google Voice -- i.e. some website where I can add a list of blocked senders, or tell the Post Office not to send messages addressed to a previous resident.
Re: Hey wait!
Also still has to pass the Senate, right? And it looks like it's shy of 2/3, so a veto could work.
Wikileaks
From a free speech perspective, this sounds similar to Wikileaks. Bradley Manning clearly broke the law by leaking information. But should Wikileaks be held accountable for basically forwarding or distributing that info?
Some dice here: SkyNews screwed up by leaking her name. Might make sense to go after them -- but it bothers me that you can get trouble for a "retweet".
Re: "The cat is out of the bag" = BS
In this case, the original leak came from SkyNews, not Twitter users. Yet police are arresting people who basically re-tweeted or otherwise passed on the information. If the police want to go after SkyNews, fine -- they screwed up. But it scares me that the simple act of pressing the "retweet" button could subject a person to criminal liability.
Creative Commons for Licensing?
Maybe standardization could help here. Most people don't read the full-text of a CC license, but they might check out the "short" version or recognize the icons floating around.
But all in all, a hard problem. People's privacy expectations on websites are informed by a mix of the UI design and their experiences with other websites. And the idea of being used over a misleading UI would terrify any designer.
How do the charts work?
Do we have to buy the song for it to be tracked? Does streaming it via YouTube count? Spotify?
Re: Re: Re: The bigger picture
Eh, it definitely applied to Costco. And I imagine that, as a big corporation, it has plenty of cash.
Re: Re:
Suppose a book is (legally) made in China. According to the 9th Circuit, the copyright holder can prevent you from importing the books into the U.S. and reselling them.
BUT suppose the copyright holder itself imports in those books and sells them. Now you can resell the books.
Re:
That's the rule in the 9th Circuit at least. See OMEGA SA v. Costco Wholesale Corp. and Parfums Givenchy, Inc. v. Drug Emporium, Inc.
Re: The bigger picture
Unfortunately, it's not that easy. The implication of the Second Circuit case is NOT that if something is made overseas, then U.S. copyright law ceases to apply. Rather, it's that if it's made overseas, it is no longer "lawfully made." That is, everything made abroad is essentially unlawful (under U.S. law) and the minute it touches U.S. shores, it can be blocked by the copyright holder.
Re: Re: Re: Re: Nobody Needs To Know
Depends how easy it is to launch a class action lawsuit over their crappy meters.
So their's unfortunately, but we can blame Congress / The Supreme Court for that.
Re: Re: Nobody Needs To Know
The meters could be implemented by the OS. Android and iOS don't have any incentive to misreport data usage.
Agreed that metering is the better way to go though -- meters degrade gracefully, so going a little over a cap won't kill you.
This isn't unique to MBs
Ever try going on a diet and guessing how much a calorie is? Or how many kilowatt-hours of power you use? Or cubic feet of water?
We have varying solutions to the above, albeit with mixed degrees of success. It's a hard problem.