If you too are just now catching up with the Cooks Source train wreck, this LA Times blog entry is a good place to start. A small, low budget regional food publication printed a blogger’s post without permission (apparently this is the only event that is clearly documented and an uncontested fact) and when the writer protested, the editor or someone using the email of the editor of the publication wrote back and said everything on the web is public domain and the writer should be glad they were not sending her a bill for editing the piece.
I don’t have the complete chronology but apparently it was last Thursday, November 4, that all hell broke loose. Just before midnight on the 3rd, the blogger posted her account on her own very eclectic blog and by the next morning the story was everywhere including the LA Times. At some point it was discovered that Cooks Source had a Facebook page and that was when the pile-on began.
Some time during the day on November 4, the editor or someone with access to her account posted on FB, “Well, here I am with egg on my face! I did apologise to Monica via email, but aparently it wasnt enough for her. To all of you, thank you for your interest in Cooks Source and Again, to Monica, I am sorry — my bad! You did find a way to get your “pound of flesh…” we used to have 110 “friends,” we now have 1,870… wow!”
But of course, those “friends” were simply “liking” Cooks Source so they could post. The comments, assuming they are still there, are pretty funny for the most part but the whole experience certainly adds up to a public dunking or time in the stocks, which is appropriate considering that the original recipe was from a blog on medieval cooking.
After all that I got around to checking out the actual Cooks Source website, where there was an announcement that the magazine has taken down its website (sic), and shut down its Facebook page as of 6 pm on November 4. Unfortunately, the announcement continues, the Facebook page is still there because it has been taken over by hackers. I wonder what the Cooks Source people thought they were doing and if they know it is actually pretty simple to take down your Facebook page if that is what you want to do. I hope nobody tells them because like I say, this is an entertaining read. Also, on the bottom of the non-website Cooks Source page there is an apology to the blogger which seems sincere.
This is a cautionary tale for how there really is no privacy on the web and no place to hide once you make a mistake. This particular editor (or some devious person portraying her) offended a particularly vocal segment of the population and apparently did not have the good sense to make a full and complete apology in time. Crowing about the situation on Facebook, if indeed she did this, was gasoline on the flames. If you’re wrong, or simply if you decide for your business survival to say you’re wrong, the only possible course of action is to apologize repeatedly, abjectly and without reservation to anyone who will listen. RIP Cooks Source.