Slashdot Mirror


Millions of Blogs Knocked Offline By Legal Row

another random user writes with this excerpt from the BBC: "A row over a web article posted five years ago has led to 1.5 million educational blogs going offline. The Edublogs site went dark for about an hour after its hosting company, ServerBeach, pulled the plug. The hosting firm was responding to a copyright claim from publisher Pearson, which said one blog had been illegally sharing information it owned. ... The offending article was first published in November 2007 and made available a copy of a questionnaire, known as the Beck Hopelessness Scale, to a group of students. The copyright for the questionnaire is owned by Pearson, which asked ServerBeach to remove the content in late September."

4 of 162 comments (clear)

  1. Re:It's actually worse than stated... by BMOC · · Score: 5, Funny

    I was trying to be vague to avoid any possible DMCA takedown notice, now see what you've done...

    --
    I swear they give me mod points to shut me up.
  2. Obligatory reference by Anonymous Coward · · Score: 3, Funny

    I sense a great disturbance in the blogosphere, as if millions of voices suddenly cried out about useless bullshit, and were suddenly silenced...

  3. Re:It's actually worse than stated... by chalkyj · · Score: 5, Funny

    What sort of world would we be living in if you couldn't make a big fat profit out of suicide prevention? Certainly not a world I'd want to live in...

  4. Re:A good reason to host your own blog by sjames · · Score: 3, Funny

    That's no big deal for much of the demographic here, but it might as well be written in Aramaic for a lot of people who just want to blog a bit about things that interest them.

    Put another way:

    1. Just get a cheap hosting solution [google.com] (preferably outside Mafia territory), (so not in Italy or NY?)
    2. upload the decompressed [rarlab.com] archive to the wrong directory using a FTP program [filezilla-project.org], (Not working, gotta call provider)
    3. Pester hosting provider that you can't see it until someone takes pity and does the mv for you (many more calls)
    4. Point your browser at the domain (gotta call again)
    5. Make wild guesses about the gibberish it asks you about, leaving the configuration wide open to exploitation (oooops)
    6. Mark the config file read only on your PC (ooops again)
    7. Become a leading provider of Neo-Nazi propaganda (what the hell is that filth doing on MY blog?)