Well, that was unpleasant

WELL, THAT WAS UNPLEASANT…. As you’ve probably noticed, the Washington Monthly was knocked offline for quite a while, and just recently recovered. Complicating matters slightly, the site was back up before I could get into the administrative page to add new content. But we seem to be back in business now — except for maybe the comments section, which is still having some trouble.

I’m still a little sketchy on the details, but as I understand it, an unknown party attacked the site at some point last night, and did an enormous amount of damage. Thanks to a lot of hard work this morning, we’re back up and ready to go. (If readers find unresolved tech problems, please let me know.) We appreciate all the supportive emails and tweets, as well as your patience.

Also, during the outage, I went ahead and wrote a bunch of posts that I would have published earlier were it not for the difficulties. Unfortunately, given the usual speed of the blogging news cycle, these posts now seem stale and dated, but since they’re just sitting here, darn it all, I’m posting some of them anyway. (They were fresh and interesting when I wrote them nine hours ago. Honest.)

And now, back to the news….

Support Nonprofit Journalism

If you enjoyed this article, consider making a donation to help us produce more like it. The Washington Monthly was founded in 1969 to tell the stories of how government really works—and how to make it work better. Fifty years later, the need for incisive analysis and new, progressive policy ideas is clearer than ever. As a nonprofit, we rely on support from readers like you.

Yes, I’ll make a donation