|
|
|
|
|
by darawk
2961 days ago
|
|
> In this case there is no contract. The websites are really giving their things away for free, only with the expectation , but no guarantee, that some users will see ads. This does seem to be the crux of our disagreement. You think that offering up your content merely represents a non-binding expectation. In other domains, we don't take that position. If I weave you a scarf, and I say "Hey, i'll give you this scarf if you go to the store and pick up some cough medicine for me", and then you take the scarf and refuse to go to the store for me on the grounds that I "merely had the expectation, but no guarantee that you would go to the store for me", that seems pretty odd. I'm curious: A) Whether you believe these situations are different And B) If you believe they're different, why. |
|
On the web, we have a way to handle the exact equivalent to your scenario. We do that by ensuring the user agrees to go to the store before handing them over a scarf. For instance, on the protocol level, you could reject all GET requests that do not have attached the proof of acceptance of the cough medicine quest. The rejection message (e.g. 403 Forbidden) would contain a machine-interpretable requirement of the quest. That synergizes well with the legal level - faking proof of quest acceptance would (AFAIK) constitute unauthorized access to scarf under CFAA. At the same time, the valid proof could match the legal definition of informed consent. It also meshes well with the social level, as whoever reads the 403 response (e.g. in their browser) would see the need to consent to the quest in order to get the scarf. Consenting to the quest, taking the scarf, and then not doing the quest would rightfully classify me as a thief and an asshole.