"Illegal" would seem to be a good start in many jurisdictions.
For example, as described in the article, I can't see how this behaviour doesn't fall foul of computer misuse and fraud laws in the UK. The best defence might be that somewhere buried in the terms and conditions it's allowed, but I wouldn't like to be the Microsoft lawyer arguing that position before a judge.
Are Blizzard up-front with their users about what is happening? The covert nature (or otherwise) of the uploads is a significant concern here. The average geek playing with Linux doesn't complain about BitTorrent also uploading the distro image they're downloading, but the average geek playing with Linux knows the deal and decided voluntarily to participate.
MS may run into some liability for inducing data overages depending on how up front they are about it and how badly it bites people.
I would expect that if the report is accurate and if this behaviour was activated without the user's knowledge or consent then Microsoft would be on the hook for any and all damage caused as a result. That could mean a small extra charge from an ISP for bandwidth over a cap. However, if the behaviour means someone's Internet connection didn't have enough capacity left to do something important that it otherwise would have, whether because the uploads themselves limited the spare bandwidth at the same time or perhaps because it triggered some sort of degraded service from the ISP after going over a cap, that could also mean compensation for any consequences of that degraded capacity.
I remember when people thought BitTorrent would revolutionize file hosting. Now people think it's stealing bandwidth.
Don't know why ms didn't play it safe and put internet resharing as an opt in...
Oh and I don't remeber but I think you can't set a wired connection as metered.
1: https://torrentfreak.com/spotify-starts-shutting-down-its-ma...
Back when the only data center was in Stockholm, the only way to meet latency requirements was P2P. Now that we're a grown-up company we've disabled that and use CDN's instead.
That was not their aim at all. Their aim was lowering bandwidth costs by shifting the content delivery costs over to the end users. This was made clear by the fact that when you played a song, it started downloading the song from AWS S3 immediately to minimize latency, then once the P2P sessions fired up, shifted over to that stream instead of their costly S3 one.
This isn't transparently helping serve updates to computers on a local network to save bandwidth. It transparently serves updates to the entire world, to eat your bandwidth and conserve only Microsoft's.
Is there a word in English that captures how massively disappointed I am with this being on every Win10 computer and by default?
[1]: http://hints.macworld.com/article.php?story=2007100908224845...