Slashdot Mirror
Hacker Crackdown?
rombouts noted that Salon has a good piece on the liability of programmers. From Napster, to Freenet, to DeCSS, on down. If you're scared by any of this, you should be. There are a lot of cases out there right now that are gonna change the world, and folks, it could go either way.
Creating laws which cannot be universally enforced leads to arbitrary enforcement
OK, I'm kind of stating the obvious there, so I'll explain further. If we as a society create laws which have no hope of being enforced consistently because of the number of people already breaking these laws, then we are opening the doors to abuse by the government and police. We end up with a society in which everyone is guilty of something, but the only ones being punished are those who are disliked for some reason. The reason can be just about anything. You give the example of racism, which is a very good one, but is also unfortunately only the beginning. We could end up with a society in which a reporter uncovers some dirt about somebody in power, and ends up going to jail because of it. Sure, the reporter in question could never be directly prosecuted for uncovering dirt (hopefully, although the way our society is going...), but those in power might tell the police to go and arrest the reporter for a crime that everyone commits. This creates an atmosphere in which people are afraid of criticising their leaders. Unfortunately, we are already headed down that path. How many of you can honestly say that you never do anything illegal, and that if the police were watching you 24 hours a day they could find nothing to arrest you for?
Unfortunately, more and more laws are being made that can never (and should never) be effectively enforced. It's not part of a grand conspiracy, but the end result is the same. The reason is simply that the people are always screaming for the goverment to do something, but they never seem to care whether or not what the government did had any effect. They just want laws to "protect the children" and whatnot. But this doesn't simply result in a bunch of worthless laws that we can all laugh at and go home. It ends up creating an environment that is practically asking for government abuse. And abuse they do. And it's only getting worse...
I am not an idiot. Please use my name to email me.
"That's right, I'm quoting myself."
-Upsilon
I think this issue makes more sense when you divide it into two:
The salon article uses the industry that gave us guns, bombs, car and pantyhose as examples of product's creators being separated from the usage of their products. Their argument was valid five years ago, but today it's shot to hell:
When you take a step back from our little microcosm and look at the rest of the world, you can see the growing trend of companies being held accountable for the usage of their products - either intended, in the case of tobacco, or unintended, as with the gun industry. The system is primed and ready to take poor Shawn Fanning and his little Napster upon the gallows for a good ol' public execution. Hanging might have gone the way of the Dodo, but the effect is going to be the same.
The second issue is accountability of software authors, specifically. Hey folks - if you've just been skimming, pay attention now and let me tell you something: Holding software authors accountable for their software is a good thing! (It's also inevitable, but you'll see that) I know I'll get flamed for saying that, but give me a second.
This discussion comes up on Slashdot about once a month. Folks gripe about companies paying the kid down the street to make them a web site, because the kid will do it for far cheaper than a real professional, and have similar results. But once the kid delivers, the company still doesn't have the product it was looking for. So then, they come to the professional.
There needs to be a way to differentiate between you, the professional software engineer, and the kid next door. Sure, you can get MCSE, CNA and a whole slew of other acronyms after your name, but that's not working. Every other engineering discipline has a certification exam that allows you to personally ceritfy yourself as a Professional. Once you're a Professional Engineer, you're held responsible for your work. Civil Engineers are held liable for their bridges, Mechanical Engineers for their machines, and it's a Good Thing. It forces the engineers to hold to their design process and keep the level of quality high.
Every software engineering text that I've read supports this trend towards accountability. The process of creating large software products is slowly becoming more and more of a formalized process. Formal procedures are good, because software design is inherently a very difficult process to make step-by-step. Changing requirements, ignorant customers, bad technology, they all work aganist you. This formal specification of the software design process creates accountability, in the form of Software Requirement Specifications (SRS). A contract, between the company and the customer, outlining the expectations of the new piece of software. The beginning is there.
Companies are going to be held liable for their products. That's inevitable, given the larger trend in our system. But is it fair to hold a kid, be it the DeCSS kid or the Napster kid liable for making public the result of their late-night tinkering? I don't agree, but then, I've got the perspective of the tech-savvy.
Napster probably will be shut down. Shawn Fanning probably will held accountable. We're liable to see a veritable witch-hunt begin over the course of the next couple years as a result. But, in the end, the legal system as well as the software authoring world will be a more mature place. Will a formal system of accountability get set in place? (shrug) The ball is rolling. Which direction it takes down the hill, and what bumps it'll hit are unknowns. But it is rolling.
A problem
Unfortuantely american society (among others) is leaning in a direction where the individual is no longer accountable for their actions. Liability for individual's actions are being shifted to product manufacturers. This is mostly thanks to lawyers and greedy americans who think they can get the 'big score' by suing large corporations. Additionally large corporations use lawyers and litigation to intimidate individuals out of behavior that while technically legal is contrary to the way corporations believe things should be done.
You aren't responsible when you spill coffee on yourself, McDonalds is.
You aren't responsible when you get a terminal desease for using a product you knew was unsafe for twenty years, Philip Morris is.
You aren't responsbile when you shoot someone while mugging them, Smith and Wesson is.
You aren't responsible when you pirate music, Napster is.
The terrible end result of this strategy is that your individual rights and fredoms are stripped from you by government because you keep proving time and again that you do not want to be responsible to weild these rights. Government turns into a big babysitter.
Thats the big picture; damn sad where we are going. But to focus on what you can do today to protect yourself:
A solution
Anyone who is considering doing something that may draw the wrath of lawyers should consider incorporating. Incorporation provides protection to those who work for corporation so that these people are not fiscally liable for the actions of the corporation. Thus if you write something somebody does not like and you sign all rights to this code over to your corporation (and licensing this code out with GPL or equiv). Then when the lawsuit comes they can only go after whatever assets your corporation holds, rather than your personal assets.
Incorporating is fairly simple, and involves either some research on your part or paying a lawyer to get things moving. I'd say you probably won't be set back more than $1000, and probably around $150/yr to maintain it (could be more depending on which state you incorporate in and how much research and accounting you do yourself).
It's cheap insurance if you anticipate legal threats. One caveat is to ensure you act within your corporation's framework; if you do things that blurs the line between you 'the corporation' and you 'the individual' you could become personally liable again.
-- Greg
IANAL, so go seek one's advice if you'd like to learn more about incorporating and liability.
Slashdot, would a spell-checker for posting be too much to ask? It's not rocket science!
But there's the problem... they clearly will stop somewhere, even if the law doesn't make it clear why they should.
An Oklahoma law makes it illegal to possess anything that looks like an illegal drug. Clearly Oklahoma's finest don't spend all their time kicking down kitchen doors and putting people away for having powdered sugar, oregano, or water. But in 1998 they did throw George Singleton in jail for a month, even though he was able to prove that he made his living as an herb merchant and that the plants filling his car were rosemary and mullein, two legal plants that he grew to treat asthma (and which, incidentally, don't look at all like marijuana).
Anyone want to guess what color Singleton's skin was?
Making (e.g.) Clarke liable for Freenet would be disastrous. It would put us in a state where most coders and inventors would be legally liable for something, but few would ever be prosecuted. This would give the government vast latitude to punish anyone they disliked, under a legitimate but overly broad blanket -- kind of like prohibition, in which everyone drank but only undesirables got busted.
- Michael Cohn
-----
Go ahead, blame me... I voted for Nader!
Even with the unpleasant US laws on copyright and so on, I think salon are over-egging this one (and IAAL, but NAUSQL; mileage may vary from the US Bar). Look at a few examples:
In fine, the author of a piece of source code is OK. If he does something with it that is not protected, he's potentially in trouble. If he provides some other service that's an infringement of something or other, he's potentially in trouble.
That's what Napster ran aground on: the injunction (which won't get stayed by the Appeal, according to a US attorney friend of mine) was against the inclusion of copyrighted material in their searchable database of traded MP3s, not against the non-infringing uses of the software or in respect of anything the users did.
The injunction ordered Napster to do something they had previously declined to do: exercise some discrimination in the material they included in their list of tradeable MP3 files. Nothing to do with their authorship of any software.
The Oppenheimer defence is available only where you have no control over the end use of the product and there is a substantial lawful end use of same and the product is not dangerous in normal use if it is meant to be safe. (This is a statement of general principle, incidentally: for the specific application in your local jurisdiction consult a lawyer qualified to practise where you are).
Oppenheimer himself had no control over the end use, and that end use was (in the context of a major war) lawful. The product was dangerous in normal use, but then bombs are meant to be.
Big Tobacco is OK all the way up to the danger point. They've been insisting that the product was safe for decades, and now that is coming home to roost. (If they'd sold it, from when they first figured it out, on the basis that "this stuff will kill you: don't say you weren't warned that a little pleasure now will be paid for with a lot of pain later" they'd have been watertight)
DeCSS is perfectly safe to use, and there is a substantial lawful use (at least, lawful everywhere but the US) for a finished product (an executable). The source code itself doesn't do anything but communicate, so it's protected speech. The authors can't otherwise control what's done with it.
Napster, on the other hand, is used almost exclusively (on the evidence in that case, and on Napster's own business plan) for copyright infringement, and Napster run their marketplace as a centralised service so they've got a clear control over what's done with it. It is this last that caught them by the main zipper; it is this that's going to make their eyes water.
-- AndrewD
A Maze of Twisty Little Laws, All Different.
A good starting point would be:
Why should programmers be silenced for following their True will? Science is already bogged down and stupidified through the master-servant systems incorporated in all major corporations, the education system and politics. If you have to go through the burden of bureaucracy, or resort to lying to your superiors because you know your real thoughts might get you fired or failed, you're already losing control over your own creativity.Controversial or subversive material such as Socrates' philosophies, the research and books of Wilhelm Reich, or Napster, will always be suppressed by the powers that Be because of fear of the Unknown. The majority of the general public will be fooled all the time. Lawsuits and threats of financial incapacitation have just replaced the poison cup or the burning of books as the establishments instrument of oppression.
Maybe it's time to realise that electorial democracy is just another words for a self-imposed dictatorial oligarchy?
--
Pokéthulhu
Gotta catch you all!
But if I write a piece of software that can be used for file swapping and someone uses it to commit copyright infringement, I may be held responsible for contributory infringement by the RIAA and MPAA?
Even the language and analogy itself is disturbing: creating tools for letting people share information is now on the same level as creating nuclear bombs? Isn't the ability to communicate freely at the heart of a democracy?
I think it's pretty clear what the deciding factor is in who can and cannot be held responsible for the software they create: people with money and political influence are exempted from responsibility. Remember that next time you vote and give the third party candidates a chance. Nader is looking pretty good...
The article refers to making programmers accountable for the ways their software is used against other people, not for how good the software is. This is very different from the liability the automobile and tobacco companies are fighting. This is more like the lawsuits being pressed against the gun makers.
That being said, this concept (programmer is responsible for how his program is used) is ludicrous. While it is important for people to be aware of the potential uses of their creations, the leaders who gave the orders to drop the atomic bomb are to blame, not the scientists who designed it or the works who built it.
This issue is very complex. There is a lot of energy at stake, and a lot of confusion about what can and what "should" be done. The only sure way to solve all these problems once and for all is to hold the final decision makers responsible for _their_ actions. If you are holding a gun, only use it in self defense or for sport. While driving a car, respect the power of 2000 pounds of steal going 70+ mph. While holding a baseball bat, don't blame the manufacturer if you decide to hit someone with it.
No matter what power you hold, there is noone better qualified to keep you from abusing that power than you.
Blaming doesn't get us anywhere. The change we want is much deeper than making it more difficult to cause harm. We need to stop wanting to cause harm.
(We also need to agree on what harm is - napster is certainly a grey area in many peoples' minds.)