"Bob, if you should ever need to delete 100% of the content that I've created for you, you would follow this URL. Let me be clear, it will destroy USD $1,000,000 worth of goods."
Never rely on your environment to differ between the various HTTP methods for you.
"In particular, the convention has been established that the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered "safe". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is made aware of the fact that a possibly unsafe action is being requested."
The document section also makes a distinction between "safe" and "idempotent" methods. That's not the same thing.
A less naive implementation would also include a crumb to mitigate CSRF as well as unintentional access.
Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N > 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property.
1. There is probably something in the EULA for Skype that MS put in there to cover themselves with respect to this.
2. If there is not, it might be more effective to try and bring a multitude of small claims court cases against them. A tactic that worked against Dell in at least one instance: http://consumerist.com/2006/12/13/man-sues-dell-and-wins-by-...
The machine excuse is inoperable - the agreed mode of operation of such machines is to refuse to follow links in a robots.txt file. If the machine has been programmed to ignore this de facto regulation then there's mens rea to go with actus rea performed by the machine for and at the behest of those who programmed it.
I can't program a tank to drive me on to your land and then claim that I haven't committed the tort of trespass, same goes here.
IANA(IP)L either, but sometimes I play one on the internet.
Also, mens rea (i.e., "guilty mind" or colloquially, intent) is a criminal law concept that has no relevance in the civil/tort law realm. It doesn't matter whether the machine has been programmed to ignore robots.txt because no law requires a software program to obey robots.txt.
If that line holds then the corollary appears to be that programming a robot to duplicate linked content deny-ed by robots.txt is certain copyright infringement.
Copyright law is a weird one, it sits in a sort of limbo between tort and crime hence it seems relevant to not only consider the balance of probabilities and the test for tortuous infringement but also the criminal considerations. Moreover in various jurisdictions it's a crime to access a part of a computer system without authorisation, this would appear to apply to MS's directorship in this case; such laws might "require" obedience to established protocols for determining if access is authorised [would be interested if anyone reading can cite caselaw to support/discredit this line of thinking].
MS download and you've got them on copyright infringement for which there is no apparent excuse outside of wilful negligence.
What's the multiplying factor the MPAA use for copyright infringement, something like 1000 times the regular licensing fee.
...
4) Profit