The article is somewhat poorly written with the chronology being difficult to follow, but this is what I made of it: 1. the Edublogs team removed the offendin

The article is somewhat poorly written with the chronology being difficult to follow, but this is what I made of it: 1. the Edublogs team removed the offending post within the 12 hours, thereby complying with the request. 2. apparently ServerBeach took it upon themselves to double check through presumably automated means and detected the file in a Varnish cache (which would be inaccessible to the public) 3. this led to ServerBeach deciding to shut down Edublog's servers on the grounds of non-compliance. If my interpretation of the jumbled order of events is correct, it's pretty clear ServerBeach is at fault here - it's not illegal to have a copyrighted file on your server; it's illegal to serve that file without proper rights. Their system is flawed.