Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"Policies designed to not be read need to be considered completely invalid."

I think this is key. The law assumes that contracts are a big deal for both parties, that they are relatively rare, and that they're given attention on both sides.

But it's hard to get through daily life anymore without signing a ton of contracts. Software update for your phone? Contract. Sign in to some random online service? New T&C I have to agree to i.e. contract. Pay for something with a credit card? That's a mini contract you're signing.

Now, in some cases there's no real excuse for not reading a contract. To take a random example, if you sign up for a two-year contract with a cell phone provider and you're given a stack of paperwork and you sign without reading through it first, I'm comfortable saying that's on you. This isn't something you do often and you have ample opportunity to read the thing first.

On the other side of things, Apple keeps tossing these gigantic contracts my way whenever I do much more than breathe. I'll literally get fifty or sixty pages of contract when trying to download a software update or just sign into the store after they made some random change to their T&Cs. Nobody reads these things. I know it, you know it, Apple knows it, and because of that they should be strongly limited in what they can do.

I think an important test for a contract should be asking the hypothetical question, "what if everyone who signed it read through it in detail first?" For something like buying a house, this would obviously change nothing. For a cell phone contract, it would change little. For random gigantic software EULAs and web site T&Cs and similar things, it would drive all the customers away. If having everyone read through it before signing it would break the process the contract was made for in the first place, the contract shouldn't be valid.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: