Monday, 13 July 2009

  • Guiness Book of World Records threatens to sue Failblog, gets rick rolled back!

    This is fricking epic.  First, Failblog posts a fail where Guinness displays the record for "Most Individuals Killed in a Terrorist Attack", and then urges readers to "Break This Record"!



    How does the Guinness Book of World Records respond?  By threatening them with a lawsuit!  Classy.



    So Failblog writes one of the best replies to any legal threat ever... and tosses in a rick roll too!

    Dear Sir/Madam,

    Thanks for writing us an email regarding the “Record Breaking Fail”. Unfortunately, douchebaggy cyber-bullying emails will only bring upon you more shame on your house. I am also resisting the urge to write this email in ALL CAPS.

    I believe it is the duty of FAIL Blog(TM) to call out organizations when they encourage the public to do such things as “Break the record” for the “Most Individuals Killed In A Terrorist Act”. We firmly believe that our publication of your fail is protected under the concepts of fair use, commentary and non-trademark use. Please RTFM and we welcome you to teh interwebs.

    Since we at FAIL Blog(TM) don’t have a legal defense department, we have complied with your request to remove the trademarked term and logo from the original image. We have used the “naughty bits filter” on the image to secure your naughty, naughty, trademark assertions. However, we have posted your email so that our audience can see why we had to remove the name of the failer from the image. I hope that this is the outcome you have expected as now NO ONE WILL EVER KNOW THAT GUINNESS WORLD RECORDS LIMITED HAS FAILED.

    The full legal response can be read here: icanhaz.com/legalresponse

    Cheers,
    FAIL Blog

    P.S.: This is what we think of your letter.


    Guiness Book of World Records: DOUBLE FAIL!!

    My favorite part is that Failblog's response is called, "OMG U FAIL SO HARD".

Comments (35)

  • Choose Identity

  • Give eProps (?)

  • New! You can now edit your comments for 15 minutes after submitting.