Chebucto Regional Softball Club

Kernel-level anti-cheat? _\*reads article \*_ Kernel-level anti-cheat. So not a _real_ compatibility issue, just fixing an artificial one _they_ created.

Starfield was like a child's half-inflated balloon: let go with high hopes only to immediately disappoint, then swiftly forgotten once it drifted out of sight. Bethesda wanted to reach the stars, yet only managed to drop trash in someone's garden.

This seems pretty normal to me. Isn't this how it already works? It's better than content hosts being held liable by default. Without a safe harbor provision (where you're only liable if you don't remove items you're made aware of), file sharing would be a non-starter in those countries.

It sounds like they didn't, but apparently Microsoft forgot to put together a contract for further work they were doing for the MCC, so they were able to hold the Xbox One port of Halo Anniversary hostage contingent on Microsoft removing the clauses blocking royalties. So they did get royalties for _that_ port that amounted to tens of millions of dollars, but nothing for their original work.

They eventually did, but apparently only because Microsoft forgot to finalize a contract for further work they were doing, meaning they were able to hold the port of Halo Anniversary to next gen hostage contingent on Microsoft removing the clauses blocking royalties.

And then Microsoft screwed them out of royalties, according to the article. I feel like they should have included that in the title.