Paul misspoke -- sort of.
What irritates me are contracts (particularly contracts of adhesion) in which the other party has no intention of enfocing certain provisions. Such provisions are included so that they can be called upon when someone does *something else* that they do not like, particularly something that they did not expect.
For example, my contract with Road Runner, my former cable modem provider, said that I was absolutely not allowed to run a server off my cable modem. But the company knew and had no objection to my using a Linux box as a gateway machine, even though it was technically a server.
What the "no servers" provision of the contract wanted to prohibit was people using their cable modem connection in order to serve web or ftp sites that would suck up lots of traffic. The contract prohibited more than it needed to, so that Road Runner could bounce bandwidth-sucking users on the grounds that they had a server, rather than on the grounds that they were sucking up bandwidth.
Such contracts are frequently overly broad because there are no incentives to make them actually prohibit only the things that the contracting company needs to prohibit. Consequently, companies exclude all manner of things that are just fine, thereby giving otherwise reasonable people a reason to lie about their activities so that they are not in violation of the contract.
The danger to the company is that once people see it as okay to lie to the company about X, they are more likely to lie in cases where it does actually matter.
Contracts of adhesion make this situation all the more difficult, as it is more or less impossible to negotitate more reasonable terms or get legitimate permission to violate those terms. Hence, the incentive to lie is greater.
So that's what bugs me about contracts of adhesion. |