Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/33/d214989360/htdocs/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/33/d214989360/htdocs/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/33/d214989360/htdocs/wp-includes/http.php on line 61

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/functions.php on line 31

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 51

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_width() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/header.php on line 8

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166
Category Archive for ‘ND-Pres’ at Campaign Diaries
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archive for the 'ND-Pres' Category


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Battleground watch: Race heats up in Arizona, McCain scales back turnout efforts

In the final stretch before Election Day, campaigns typically focus on an increasingly narrow list of swing states - but this year new battlegrounds are emerging left and right.

A few weeks ago, West Virginia suddenly looked like a very promising state, and though recent polling has not shown the race to be that competitive, the Obama campaign did buy air time. We also started hearing about a potential Obama investment in Kentucky - though that does not appear to have come to pass.

But the Obama campaign just announced that it would start or resume advertising in three red states: Georgia, North Dakota and McCain’s home state of Arizona. Obama advertised in the first two states throughout the summer, only to scale back his efforts in mid-September when it appeared that McCain was finally putting marginally competitive red states away. But both have now tightened, so much so that the Atlanta Journal Constitution is calling Georgia a nail-biter.

The real stunner, however, is Obama’s decision to make a play for Arizona. No one doubts that Arizona would have been a highly competitive race had the Republican nominee not been the state’s Senator, but it is very rare for a candidate to lose his home state (Al Gore’s failure to hold on to Tennessee cost him dearly, but Gore had not represented his state in years).

But Obama’s strength among Hispanics and among Western independent voters give him a shot at picking-up the state’s 10 electoral votes. A surprising deluge of Arizona polls have been released over the past few days, and nearly all have shown the race within the margin of error. (A new Research 2000 poll shows McCain’s lead down to 1%.)

Et tu, Arizona?

(It is interesting to see that Obama’s ads in the state will be a positive one, whereas he is airing attack ads in Georgia and North Dakota; similarly, Move On is also going up on air in Arizona on Obama’s behalf, also with a positive ad. Democrats apparently do not want to antagonize Arizona voters who have a long relationship with the Republican nominee.)

Whether or not the state will fall to the Obama column is not as important as the fact that the McCain campaign has been forced to schedule its final rally on Monday night in Arizona. That’s right, the very last public event held by McCain before Election Day will not take place in a giant Florida auditorium or against glorious Virginia backdrop - venues that could generate some much-needed momentum for the GOP - but in Arizona, whose 10 electoral votes where the last thing on anyone’s mind until this past week-end.

This development alone summarizes McCain’s predicament: He has been forced to scale back his efforts in all blue states except Pennsylvania (as the latest list of the campaigns’ state by state spending confirms) and has had to invest more and more time defending red states that Obama absolutely does not need but where a victory would seal an electoral college majority: Arizona, Georgia, Indiana, Missouri, even North Carolina - none of these are in the top tier of states that are expected to get Obama above 270, but McCain is so weak in all of them that he has to take time away from Nevada, Colorado, Virginia, Ohio and Florida - all states he also needs to win!

That the McCain campaign is now forced to implement a national strategy in the hope of narrowing the gap nationally and in the process gain in some of these red states is evident in the remarkable news (reported by the Washington Post) that McCain is scaling back the GOP’s famed 72-hour turnout operation to invest more money on TV ads.

At first, this decision can seem insane: McCain is already facing a huge organizational disadvantage, so why would he dig himself in a deeper hole? But his campaign has no other choice: The 72-hour program is meant to win close races, and it can certainly perform beautifully (and a large share of Bush’s victory can be attributed to his top-notch turnout effort). It is not meant to move the race by more than a couple of points - and that is McCain’s task now. He has to close a high single-digit gap in Colorado, Virginia, Pennsylvania and perhaps Nevada. Unless he shifts momentum, convinces undecided voters and some voters who have already settled on Obama, no amount of organizational muscle will allow him to mount a comeback.

In other important news from battleground states

  • The North Carolina Board of Elections has agreed to extend early voting by four hours on Saturday, meaning that voters can cast a ballot until 5pm on the first day of the week-end. Democrats were worried that thousands of voters would be left unable to cast a ballot had the polls closed at 1pm. This follows a decision by Florida Governor Charlie Crist to extend voting hours by four hours a day all week.
  • A federal judge ordered Pennsylvania’s Secretary of the Commonwealth to distribute paper ballots.
  • In Colorado, more than 35,000 new voters who requested mail-in-ballots are at risk of having their ballot disqualified because of voter identification rules.
  • In a blow to the GOP’s plans to challenge voters at the polls on Tuesday, a judge ruled that Ohio residents do not have to have an actual address to cast a ballot and that a homeless voter is eligible if his only “residence” is a park bench.

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Eleventh presidential ratings: Obama consolidates electoral college lead

A week after Obama surged to a dominant position, the ratings remain relatively stable, with only one state shifting in or out of a candidate’s column. There is movement under the surface, however, as McCain’s base continues to erode while Obama solidifies his hold on a number of states; a total of 26 electoral votes move from the lean Obama to the likely Obama column, giving the Democratic nominee a base of 260 electoral votes.

In my September 20th ratings - posted exactly a month ago - 18 states were listed in a competitive category (lean or toss-up). Of these, not a single one is today in a more favorable category for McCain but fourteen have shifted towards Obama. In fact, 8 of these states are no longer competitive at all - and they now all belong to the Democratic nominee. They have been replaced by four new red states that were solidly anchored in McCain’s column a month ago and are now considered competitive.

What better way to illustrate how much the electoral map has shifted towards Obama over the past month, and how most of these changes will not be erased no matter how much McCain closes the gap in the final 16 days. Unless some major event turns the campaign on its head, Michigan or Iowa, for instance, are now out of contention.

This also illustrates how narrow McCain’s electoral strategy has become: He needs to sweep nearly all of the 14 states currently rated as competitive, including all three red states that are in the Obama column. That is no small feat, and it is revealing of just how much Obama is command. That said, there is a reason these states are still listed as competitive: they could go either way, and a slight wind pushing McCain over the final two weeks could help him accomplish that.

Without further delay, here are the eleventh electoral college ratings (states whose ratings have been changed towards Obama are colored blue, those whose ratings have been changed towards McCain are colored red):

  • Safe McCain: Alabama, Alaska, Idaho, Kansas, Kentucky, Louisiana, Mississippi, Nebraska (at large + 3rd congressional district), Oklahoma, South Carolina, Utah, Tennessee, Texas, Wyoming (116 EVs)
  • Likely McCain: Arizona, Arkansas, Nebraska’s 1st district, South Dakota (20 EVs)
  • Lean McCain: Georgia, Montana, Nebraska’s 2nd district, West Virginia (24 EVs)
  • Toss-up: Indiana, Missouri, Nevada, North Carolina, North Dakota, Ohio (65 EV)
  • Lean Obama: Colorado, Florida, New Hampshire, Virginia (53 EVs)
  • Likely Obama: Iowa, Oregon, Maine (at-large + 1st district + 2nd district), Michigan, Minnesota, New Jersey, New Mexico, Pennsylvania, Washington, Wisconsin (107 EVs)
  • Safe Obama: California, Connecticut, DC, Delaware, Hawaii, Illinois, Maryland, Massachusetts, New York, Rhode Island, Vermont (153 EVs)

This gives us the following map and totals:

  • Safe + Likely Obama: 260 electoral votes
  • Safe + Likely + Lean Obama: 313
  • Toss-up: 65
  • Safe + Likely + Lean McCain: 160
  • Safe + Likely McCain: 136

I will naturally not attempt to provide an explanation for every single one of these ratings and will concentrate instead on those that have shifted over the past two weeks:

Alaska, likely McCain to safe McCain: Like in other red states Obama had been eying, McCain jumped to a commanding lead in Alaska in the aftermath of the GOP convention and of the Palin pick. Unlike in some of these other red states (say, North Dakota and Montana), McCain’s surge has not faded over the past month. The Sarah Palin effect is strong, and it appears to have put Alaska’s once-promising 3 electoral out of Obama’s reach for good. In fact, the GOP’s recovery is so pronounced that it could very well save Sen. Stevens and Rep. Young.

Arkansas, safe McCain to likely McCain: Arkansas is very rarely polled, but perhaps there would be some interesting results to be found. The state remains heavily Democratic, though it is made up of conservative Democrats who vote GOP in federal races. Obama was not expected to do well among conservative Democrats and blue-collar voters, but the startling finding that he is competitive in West Virginia means that he is making inroads in the type of constituency that could help close the gap in Arkansas.

Maine’s 2nd district, lean Obama to likely Obama: Despite a week of GOP advertisement and a visit by Sarah Palin, the GOP does not appear satisfied with the odds of snatching away one of Maine’s four electoral votes, as we learned this week that the RNC is moving out just as quickly as it moved in to help protect red states. The McCain campaign is staying on the state’s airwaves but a recent Research 2000 poll showing Obama with large leads in both districts and statewide suggest that the RNC’s pull-out was a wise decision.

Minnesota, lean Obama to likely Obama:  On paper, Minnesota should not have been have been as vulnerable as neighboring Wisconsin or Michigan, but the polls here tightened more than in other blue states throughout August and September. But a sign of Democratic confidence came from the two campaigns’ expenditures: Minnesota is the only state in which Obama let McCain outspend him by significant amounts, signaling that he believed Minnesota remained solidly anchored in his camp. Now, Obama is matching McCain’s spending (another sign of Democratic confidence given that Obama is outspending his opponent by massive amounts in every other battleground state but Iowa), and polls are reflecting the state’s return to its Democratic roots. Obama leads by double-digits in CNN/Time, Research 2000, Star Tribune, Quinnipiac… Even SUSA now has Obama leading outside of the margin of error. Do I need to say anything else?

New Mexico, lean Obama to likely Obama: New Mexico was the second red state to move to the Obama column - and it did so early. In fact, Obama started enjoying double-digit leads in New Mexico polls well before he did in blue states like Minnesota or Michigan. One significant factor has been Obama’s strength among Hispanics; when it was still believed (back in primary season) that Obama might have problems among that group, it looked like the Southwest could be promising territory for McCain. But it will be hard for the Republican to stay competitive in the state unless he can perform at Bush’s level among Latinos - and every indicator suggests that he is underperforming.

North Dakota, likely McCain to toss-up: Three successive polls released over the past week have found an Obama lead or an exact tie in a state that Democrats abandoned in mid-September, after McCain’s post-convention surged appeared to put North Dakota and the rest of the Mountain West out of contention. With 15 days to go until Election Day, there is increasing speculation that Obama is looking to put resources in the state in a last-minute bid to recapture its electoral votes - and polls indicate that would be a wise decision. One interesting fact about this state is that it does not have any voter registration: any one who has lived in a precinct for the past 30 days can show up and cast a ballot.

South Dakota, safe McCain to likely McCain: The latest polls from the state find a large lead for the Republican nominee, but we have had no result since mid-September. Since then, Obama has made gains in the Mountain West, and it is unlikely that he has been able to tie the race in Montana and North Dakota without also making some inroads in South Dakota.

Wisconsin, lean Obama to likely Obama:  Among the tightest states of the 2000 and 2004 contests, Wisconsin does not look like it will be decided in the early hours of the morning this year. In fact, the Badger State never emerged as a true battleground this year; only during a brief patch in mid-September did Obama’s lead descend in the mid single-digits - certainly nothing to be panicked about. Since then, Obama has recaptured a double-digit lead, and while Quinnipiac’s 17% margin might be overstating his advantage, but the Univ. of Wisconsin, SUSA, or Research 2000 aren’t that far off. And we got confirmation of the fact that Wisconsin is no longer in the top-tier of competitive races when the RNC’s independent expenditure arm pulled out of Wisconsin this week; it had been airing ads in the state since its very first wave of expenditures back in June.

History of Campaign Diaries’ electoral ratings:

  • October 20th: + 153 Obama (313 for Obama [153 safe, 107 likely, 53 lean] and 160 for McCain [116 safe, 20 likely, 24 lean])
  • October 12th: + 150 Obama (313 for Obama [153 safe, 81 likely, 79 lean] and 163 for McCain [122 safe, 17 likely, 24 lean])
  • September 27th: + 55 Obama (239 for Obama [154 safe, 43 likely, 42 lean] and 174 for McCain [122 safe, 38 likely, 14 lean])
  • September 20th: +6 Obama (222 for Obama [154 safe, 19 likely, 49 lean] and 216 for McCain [119 safe, 41 likely, 56 lean])
  • August 31st: + 16 Obama (243 for Obama [154 safe, 29 likely, 60 lean] and 227 for McCain [93 safe, 75 likely, 59 lean])
  • August 20th: + 14 Obama (238 for Obama [151 safe, 32 likely, 55 lean] and 224 for McCain [90 safe, 75 likely, 59 lean])
  • July 30th: + 38 Obama (238 for Obama [151 safe, 42 likely, 45 lean] and 200 for McCain [90 safe, 75 likely, 35 lean])
  • July 16th: +28 Obama (255 for Obama [150 safe, 43 likely, 62 lean] and 227 for McCain [90 safe, 78 likely, 59 lean])
  • July 2rd: +11 Obama (238 for Obama [143 safe, 50 likely, 45 lean] and 227 for McCain [93 safe, 78 likely, 56 lean])
  • June 18th: +22 Obama (238 for Obama [86 safe, 97 likely, 55 lean] and 216 for McCain [87 safe, 87 likely, 42 lean])
  • June 4th: +20 McCain (207 for Obama [76 base, 107 likely, 24 lean] and 227 for McCain [97 safe, 77 likely, 53 lean])

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: McCain can latch on a few trends but Obama leads in NV, CO and MO; Merkley, Rooney, Guthrie and Kosmas ahead

Just as yesterday, this roundup of poll shows that Barack Obama remains in a dominant position but that John McCain is by no means out of the race. Republicans can latch onto small trendlines in their favor in the Research 2000 and Battleground tracking polls, or to the fact that the first night of post-debate polling has not moved the numbers in Rasmussen and Gallup despite Wednesday night snap polls that had Obama winning the debate decisively. Furthermore, SUSA released the first post-debate poll of Florida today, and it is the first survey since September to have McCain in the lead – albeit within the margin of error.

That said, Obama continues to get the lion share of good news, starting with post-debate leads outside of the MoE in Nevada, Colorado and Missouri – any of which would get Obama to the White House (yes, even Nevada by itself, since Obama needs 5EVs to get to a tie, which favors him). Furthermore, a new poll from North Dakota finds a tied race – the third poll in a row to have the two candidates within the margin of error (the two previous ones had Obama narrowly leading) which confirms that North Dakota is back in play.

Over the next 17 days (!), pay particularly close attention first to the blue states where Obama has seized a double-digit lead in order to see whether there are any signs of McCain inching back to a more competitive position (for now, there are none); second, to Colorado and Virginia, where most polls show Obama with a decisive lead (in fact, many voters have already started sending in their ballots in Colorado). McCain can defend North Carolina, Missouri, Nevada, Florida and Ohio all he wants, it won’t do him much good unless he can close the gap in the Centennial State and in the Old Dominion. On to the full roundup of the day’s polls:

  • The tracking polls find Obama leading, though there is no consistent trend. Research 2000 continues to have Obama leading by double-digit (52% to 42%) though his edge in Thursday’s sample alone had dropped to 6%, and Hotline now has Obama up by the same margin (50% to 40%, a two point gain for the Democrat). Research 2000 holds at 50% to 46%, Zogby holds at 49% to 44%. In Gallup, Obama leads 50% to 43% among registered voters, 51% to 45% among likely voters and 49% to 47% among a traditional model of likely voters. Two other tracking polls I rarely mention: Obama leads by 4% in Battleground tracking (-2%) and by 5% in IBD/TIPPP (+2%).
  • Obama leads 52% to 45% in a Rasmussen poll of Colorado. He led by 6% ten days ago. Obama gets 93% of the Democratic vote and even leads among men by 2%.
  • Obama leads 50% to 45% in a Rasmussen poll of Nevada. He led by 4% ten days ago.
  • McCain leads 49% to 47% in a SUSA poll of Florida. He led by 1% two weeks ago. Republicans outnumber Democrats by 4% in the poll, a greater margin than in 2004. The good news for McCain is that he has an 8% lead in Central Florida. This poll was taken after the debate.
  • Obama leads 58% to 35% in a Research 2000 poll of Florida. He led by 5% last week. This poll was taken right before the debate.
  • Obama leads 52% to 46% in a Rasmussen poll of Missouri. He led by 3% in a poll taken Sunday; this survey was taken Tuesday night, before the debate.
  • The candidates are tied in a Research 2000 poll of North Dakota. A mid-September poll had McCain leading by 13%.
  • McCain leads 50% to 46% in a Research 2000 poll of Mississippi. Obama gets 15% of the white vote.
  • Obama leads 59% to 35% in a SUSA poll of California. If the final margin is anything close to this, can Obama possibly not win the popular vote?

Meanwhile, in down-the-ballot polls:

  • Prop 8 still leads in SUSA’s poll, 48% to 45%. More worrisome - Prop 8 leads among the 19% of voters who have already cast a ballot, 47% to 45%.
  • Merkley leads 47% to 41% in a Research 2000 poll of Oregon’s Senate race. He led by 5% three weeks ago.
  • Mark Udall leads 51% to 44% in a Rasmussen poll of Colorado’s Senate race. He led by 2% three weeks ago.
  • Sen. Chambliss leads 47% to 45% in a Research 2000 poll of Georgia’s Senate race. Chambliss led by 1% two weeks ago.
  • Sen. Wicker has a 47% to 46% lead in a Research 2000 poll of Mississippi’s Senate race. Musgrove gets 26% of the white vote. Wicker led by 5% last month.
  • Sen Landrieu leads 47% to 42% in an internal poll for the Kennedy campaign in Louisiana’s Senate race.
  • Jay Nixon leads 57% to 38% in a Rasmussen poll of the Missouri gubernatorial race.
  • In CA-11, Democratic Rep. Jerry McNerney leads 52% to 41% in a new SUSA poll.
  • In KY-02, Republican candidate Brett Guthrie leads 51% to 42% in a new SUSA poll. Guthrie trailed by 3% in June, led by 6% in September. The trendlines are good for the GOP.
  • In FL-24, a DCCC poll has Suzanne Kosmas leading GOP Rep. Feeney 58% to 35%!

Senate: The numbers from Georgia, Mississippi and Texas all point to the danger the GOP faces on Election Night. The first two races are currently rated lean Republican in my ratings, while the third is likely Republican. There is no question that Georgia and Mississippi are highly competitive - but these are precisely the races that will push Democrats to (or above) 60 seats.

The situation is particularly precarious for Gordon Smith: Oregon’s vote is entirely conducted via mail, and voters are going to start receiving their ballots this week, making Merkley’s current lead very valuable. As for Louisiana, these numbers explain why the NRSC decided to re-invest in the state after all - but did the committee have any other number than Kennedy’s own internals? Did they even have Kennedy’s numbers? Reports that Sen. Vitter and perhaps Karl Rove pressured the NRSC to go back in Louisiana suggest that the committee’s change of heart was due to outside pressure as much as to new information from the ground.

House: The two Florida races that involve ethically challenged incumbents have broken wide open in internal surveys conducted for the opposite party. But while FL-24 is already rated lean pick-up in my ratings (and FL-16 will be upgraded to the GOP column in my rating update out tomorrow), the DCCC’s numbers do seem inflated and we will wait for independent polling of the race.

The news is also very good for Democrats in WY-AL. Trauner still faces an uphill climb since most undecided voters are Republican, but he came within a few points from toppling an incumbent in 2006, so this race is certainly a possibility for Democrats. CA, meanwhile, was one of the GOP’s top prospects but Adler’s campaign hasn’t gone so well in the past few months. But SUSA’s results from KY-02 are very good news for the GOP, as this is one of the conservative open seats the Democrats are hoping to snatch away.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: ND back in contention, OH resists Obama; Dems strong in CT-04, not in MO-06

Today’s presidential polling is rather useless since these surveys were taken before a debate - and released after. None of these polls - including the five tracking polls - tell us what impact the debate might have had. That said, they provide a useful baseline with which we can compare polls released in the upcoming days.

John McCain gets some good news in this round-up - but only because any survey that has him within striking distance has now become great news for the GOP. Rasmussen’s new Ohio poll has the candidates tied just three days after Obama seized his first lead in Rasmussen polling; and both Gallup and Rasmussen tracking polls have tightened a bit, with McCain rising to a level he had not experienced in two to three weeks. In fact, Gallup’s “traditional likely voter model” has Obama leading within the margin of error - a reminder that turnout will be key.

That said, Obama undoubtedly remains in command; the tracking polls have him ahead between 4% and 11%. Furthermore, Obama seizes the lead in a North Dakota poll - the second survey in a row (after a “Forum poll”) from the state to show that it might be highly competitive after all (Obama withdrew from the state in September). Obama also looks competitive in the race for Omaha’s district. Furthermore, he continues to consolidate his position in blue state - coming in with his biggest lead yet in Pennsylvania and expanding his advantage in Oregon. On to the full roundup of the day’s polls:

  • The tracking polls have Obama in command, but McCain has made some gains in the run-up to the debate (all the trackings were taken before yesterday’s proceedings). Obama leads 50% to 46% in Rasmussen, the first time since September 25th McCain is higher than 45%; he leads 51% to 40% in Research 2000, 49% to 41% in Hotline, 49% to 44% in Zogby. In Gallup, Obama’s lead among registered voters and the expended model of likely voters is 6% (his smallest in two weeks); among the traditional model of likely voters, Obama leads by 2%.
  • The candidates are tied at 49% in a Rasmussen poll of Ohio. The poll was taken Tuesday night, before the debate. A poll taken on Sunday night and released on Monday had Obama leading by 2%; that was the first time Obama had ever lead in a Rasmussen poll from this state.
  • Obama leads 53% to 37% in the Morning Call tracking poll of Pennsylvania, his largest lead yet in the survey! In fact, it is Obama’s largest lead ever in Pennsylvania.
  • McCain leads 48% to 44% in NE-02, according to a poll released by Democratic-form Anzalone Lizst.
  • Obama leads 56% to 39% in a Rasmussen poll of Connecticut. He led by 12% last month.
  • Obama leads 59% to 35% in a SUSA poll of Massachusetts.
  • I am only including this because I try to include every poll I find, but this is probably the least trustworthy institute we have seen lately… A CNU Virginia poll has Obama leading 53% to 47%. The previous CNU poll had McCain leading by 9% but it had sampled almost no 18-29 year old and black voters were dramatically under-represented. This time, 58% of respondents are female.
  • I also do not think much of Zogby’s self-selected interactive (online) polls, but here are there nonetheless. Zogby showed McCain leading in Pennsylvania by comfortable margins when no one else did, now Obama is ahead; Zogby had Obama ahead comfortably in North Carolina when all polls had McCain up within the MoE, now Obama is narrowly ahead. In other news: McCain is up in Ohio and Indiana, Obama leads in Florida, New Mexico, Virginia, narrowly in Colorado and Nevada.

Meanwhile, in down-the-ballot polls:

  • The candidates are tied at 47% in a Rasmussen poll of Oregon’s Senate race. Smith led by 1% in mid-September. Rasmussen does not seem to have included the Constitution Party candidate.
  • In CT-04, Democratic challenger Himes leads 48% to 45% against Rep. Shays in a new SUSA poll.
  • In MO-06, GOP Rep. Graves leads 51% to 40% in a new SUSA poll. He led by 9% a month ago.
  • In OR-05, Democrat Kurt Schrader leads 51% to 38% in a new SUSA poll.
  • In KY-03, Rep. Yarmuth opens a large 57% to 41% lead against former Rep. Ann Northup in the latest SUSA poll.
  • In MN-06, a DCCC internal finds GOP Rep. Bachmann holding on to a 42% to 38% lead.
  • In NE-02, Rep. Terry is up 48% to 47% only in an internal poll for his Democratic opponent.
  • In CA-46, a seat that was deemed safe as of two weeks ago but that the GOP has been increasingly worrying about, a Capitol Weekly article reveals that Republican internals have the race within the margin of error.

Senate: Like North Carolina, Oregon remains highly competitive in all recent polling, making it unclear why so many Republicans seem to be resigned to losing both. That said, an incumbent below 50% is rarely in a good position, and Smith’s often vicious attacks ads have not sufficed to disqualify Merkley.

House: SUSA’s survey from MO-06 is perhaps the best polling news Republicans have gotten in weeks. This is a district Democrats are heavily targeting, and that the NRCC has started to invest in. Yet, Kay Barnes has made no progress whatsoever and Graves remains in a strong position. However, the rest of the surveys bring good news to Democrats. For one, Himes is in a strong position in CT-04 while Democrats look like they have made districts that were not supposed to be vulnerable competitive (NE-02, MN-06 and CA-46).

Meanwhile, Democrats have little to worry about in many of the seats Republicans were excited about picking-up. Northup’s candidacy was supposed to be one of the NRCC’s great recruitments, but she is quickly falling in Kentucky; and OR-05 was one of only two competitive Dem-held open seats before the GOP candidate got involved in a series of scandals relating to abortion and suscipicous trips.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Obama leads in MO, OH, FL and PA; Chambliss within MoE, Merkley gains

The window is closing for McCain to alter the state of play - something he needs to do to have a chance at saving his ticket in the multitude of red states in which he is now endangered. Yet, it is Obama who continues to post impressive gains day after day, for instance surging ahead to a dominant lead in a new poll of Missouri and taking the lead for the very first time in a Rasmussen poll of Ohio.

As always, the take-away lesson of these polls is the fact that Obama looks untouchable in blue states (he has two new double digit leads in Pennsylvania) and the high number of red states in which he has either tied McCain or looks to be ahead. Rasmussen’s weekly survey of 5 red states shows that McCain doesn’t have the lead in a single one, and Obama’s advantage is outside of the MoE in Florida - a state in which he has now led in the 9 most recent polls. Add to that new Obama leads in Nevada and in North Dakota (!), a second Obama lead in Ohio and it becomes obvious that McCain needs to dramatically change the dynamics at the national level.

Particularly noteworthy are the fact that Obama is leading in two MO surveys (including 8% in SUSA) and in ND. Even if the latter poll doesn’t come from a known pollster and should thus be taken with a grain of salt, it is telling that Obama’s surge has reached such proportions that states from which he pulled out (ND) or briefly decreased his ad spending (MO) in September now show him ahead. It will take a lot of effort for McCain to put these states back in the box, let alone cut Obama’s new-found edge in more obvious battlegrounds like Colorado, Virginia and Florida. On to the day’s full roundup:

  • Obama continues to dominate the tracking polls, though his lead slightly diminishes. He leads 52% to 40% in Research 2000 (-1%), 48% to 44% in Zogby (-1%), 48% to 42% in Hotline (-2%), 50% to 45% in Rasmussen (-1%). In Gallup, Obama leads 51% to 41% (+3%) but only by 7% in a tighter likely voter screen.
  • Obama leads 53% to 43% in an ABC/Washington Post national poll. His lead is 13% among registered voters. This is a clear improvement over ABC’s previous poll two weeks ago, where Obama was ahead by 4%. Obama’s position is very strong among Democrats.
  • Obama leads 49% to 45% in a Marist poll of Ohio, including 89% of Democrats. Among registered voters, Obama leads 48% to 40%. Obama’s favorability rating has jumped up to 60%, while McCain is 54%.
  • Obama leads 49% to 47% in a Rasmussen poll of Ohio. This is the first Rasmussen poll to ever have Obama ahead in the state.
  • Obama leads 50% to 45% in a Rasmussen poll of Florida. He led by 3% in the previous Rasmussen poll.
  • Obama leads 53% to 41% in a Marist poll of Pennsylvania. He leads 49% to 40% among registered voters. His favorability rating has surged upwards to 65%, compared to 55% for John McCain.
  • Morning Call’s latest daily poll numbers from Pennsylvania have Obama leading 51% to 38%, his biggest margin yet in this tracking poll.
  • Obama leads by a remarkable 51% to 43% in a new SUSA poll of Missouri. He trailed by 2% in late September. The two are tied among white voters and Obama gets 89% of Democrats, up from 82% two weeks ago.
  • Obama leads 49% to 47% in a Rasmussen poll of Virginia. He led by 2% last week.
  • The candidates are tied in a Rasmussen poll of North Carolina. Obama led by 1% last week.
  • Obama leads 55% to 40% in a SUSA poll of New Jersey.
  • McCain leads 51% to 43% in a SUSA poll of Georgia. Obama leads among the 18% of respondents who say they have already voted.
  • Obama leads 61% to 34% in a SUSA poll of New York.

Meanwhile, in down-the-ballot polls:

  • Kay Hagan leads 44% to 39% according to her internal poll of North Carolina’s Senate race.
  • Jeff Merkley leads 46% to 41% in a SUSA poll of Oregon’s Senate race. He led by only 2% in a survey two weeks ago. Constitution Party candidate Dave Brownlow gets 7%.
  • Jay Nixon crushes Kenny Holshof 56% to 34% in a SUSA poll of Missouri’s gubernatorial race.
  • Saxby Chambliss leads 46% to 43% in a SUSA poll of Georgia’s Senate race. Chambliss led by only 2% two weeks ago.
  • Frank Lautenberg leads 51% to 38% in a SUSA poll of New Jersey’s Senate race.
  • In NV-03, Rep. Porter leads 43% to 40% in a Mason Dixon poll. The margin of error is very large, especially for an independent poll - 6% - so this is well within that.
  • In FL-25, an internal poll for the Garcia campaign finds GOP Rep. Mario Diaz-Balart leading 45% to 42%.
  • In LA-06, a DCCC internal finds Rep. Cazayoux crushing Bill Cassidy 46% to 29%, with 9% going to Democrat Michael Jackson.

Statewide: Strong numbers for Democrats, who confirm their good dispositions in Oregon and North Carolina’s Senate races (both essential to their hopes of having a good congressional Election Night). Neither Hagan nor Merkley have put the race away, certainly, but polling numbers have shifted towards both of them in recent weeks. As for Georgia, it is looking highly competitive - a late breaking race that might be remembered as the ultimate sleeper of the 2008 cycle. Whether Martin has a chance of pulling an upset likely depends on the size of the African-American turnout.

House: This is the second poll Democrats have released showing Cazayoux crushing Cassidy in LA-06. I am still as doubtful that the two Democrats combined could be 26% ahead of the Republican candidate in this conservative a district, but the GOP still has to produce any counter poll. The district is currently rated lean take-over, but that could soon change based on what the NRCC does. The Republican committee commissioned a poll from the district a few days ago. If they go out with an ad buy or release the results in the coming days, they must like their chances in the district. Otherwise, the race is indeed far less competitive than we thought.

It is as unclear what we should make of the numbers from NV-03, currently rated lean take-over. Porter is clearly vulnerable (at 43%), though he is clearly still in the game. The margin of error is large enough that it hard to draw any conclusions. As for the Florida internal polls, they confirm what we have known: FL-25 is highly competitive, while the GOP appears to have put up a solid firewall in FL-13.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Battleground watch: North Dakota is off the list

The Palin pick removed Alaska, and the Obama campaign soon came to decide that investing time and resources in Georgia was no longer worth it. Now, Democrats are giving up on a third red state they had targeted throughout the summer: North Dakota.

Not only had Obama ran ads in this traditionally conservative state, but he had also opened offices and hired staff members. Now, all 11 state offices are being shut, and the dozens of Obama staffers are being sent to neighboring Wisconsin and Minnesota - two blue states that have looked increasingly competitive over the past few weeks.

There are two (related) explanations for Obama’s move. The first is that Democrats have to play more defense than they were hoping to, and as states like Wisconsin and Minnesota are becoming more vulnerable Obama has less of a luxury to go on the offense in many states. The second is that North Dakota was no longer looking that promising. Polls throughout the spring and summer found an unexpectedly competitive race, with McCain’s lead generally within the margin of error; a poll released in early September even had Obama in the lead. But the GOP convention has energized the Republican base, and that has had a big impact on a state with deep conservative roots like North Dakota. The last few polls have shown McCain jumping to a double-digit lead.

My fourth presidential ratings were titled “The Battle of the Mountain West.” Now, only Montana remains truly competitive in the region - and even there Obama might have lost some of his momentum. Of course, Obama needs none of these states to get to the White House, and the fact that such news will disappoint Democrats is only a reflection on how much the Obama campaign had raised expectations about its winning in very red states and radically altering the map. On the other hand, the Obama campaign cannot have it both ways: They invested money and opened 11 staffed offices, while McCain had no staffers in the state. Now, they are pulling out, and that is a victory for the GOP.

A state in which Obama has managed to fully draw McCain in, however, is North Carolina. Whatever you think of the Democrats’ chances of picking up this Southern state, there is no question that they have succeeded in getting McCain to spend some of his money here - and possibly even more of his time. And that’s always part of the goal of investing in offense: Force your opponent to divert resources to defense that could have been spend on offense or on defending more obviously vulnerable states. McCain is now spending almost as much as Obama on the state’s airwaves, and he is increasing his staff level. The Herald Sun reports that they are opening new offices in the Tar Heel State, though the Obama campaign keeps a clear organizational advantage.

In other battleground news:

  • California Republicans are surprisingly upbeat about McCain’s chances in the Golden State. They point out that the GOP has a much larger operation in the state than Bush did four years ago, and claim that private polls are showing the race within 5%. (The latest independent poll we have seen had Obama leading by 16%.)
  • The Boston Globe observed a New Hampshire focus group, found more potential for Obama.
  • Another focus group - this one conducted in Florida - finds undecided voters repelled by Palin and leaning towards Obama, albeit unenthusiastically.
  • The New York Times reports that Obama-fueled black turnout could be a boost for proponents of Proposition 8, California’s constitutional amendment banning gay marriage.
  • The Pittsburgh Post Gazette takes a detailed look at why Ohio is still a swing state.
  • The Washington Post does the same in Florida and gives the recipe for an Obama victory in the Sunshine State: “First, Obama must produce the kind of huge margins in South Florida… Second, he must avoid a poorer-than-normal showing for Democrats in conservative northern Florida. Finally, he must win the battle for voters across the Interstate 4 corridor in central Florida.” Those are pretty much the same goals Gore and Kerry needed to meet, but it’s a nice reminder.

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Dead heats in Michigan, Florida as NC poll finds second tie ever; Hagan leads

There are now enough polls released every day that it becomes difficult to find a consistent trend out of all the noise. Or perhaps there is no trend to be observed other than the race’s continuing tightness. Of the four Florida and Michigan polls that were released over the past 36 hours, all are well within the margin of error.

That said, both candidates have good news in today’s poll delivery. For McCain, staying so close in Michigan in polls taken during the financial crisis is a testament to how big an opportunity this state continues to be for him. And McCain has leads outside of the MoE in Ohio and Missouri today, though the latter is not such an unqualified blessing: the GOP was hoping to be close to closing the deal by late September, but a 4% margin is not going to dissuade Obama from competing in the Show Me State. And yet another poll finds that McCain can breath easier in North Dakota.

For Obama, staying so close in Florida is a relief given that numerous polls have found McCain gaining since early August. We saw last week that McCain is now spending more than a million dollars a week in the Sunshine State, something the GOP once thought it could avoid. And Obama’s double-digit lead in Iowa confirms that the state’s 7 electoral votes are increasingly solid in his column: This is the third poll in the past two weeks to find Obama leading by double-digit (after SUSA and Selzer & Co). Finally, North Carolina’s PPP poll is only the second ever (after Rasmussen’s April poll) to find a tie. At the very least, this forces the GOP to continue pouring money in the state - something they have been doing this month.

On to the day’s full roundup:

  • The tracking polls are showing a stabilizing race: Obama took a 48% to 47% advantage in Rasmussen yesterday (his first lead in 10 days) and maintained it today; Research 2000 found Obama up 8% yesterday, and up 7% (49-42) today. Diego Hotline has Obama leading 45% to 44% for the third straight day, and Gallup showed Obama increasing his lead to 6% yesterday (hitting 50 for only the second time ever) but back down to a 49% to 45% advantage today.
  • Obama leads 43% to 42% in an EPIC-MRA poll of Michigan. Obama led by 2% in July and August. When respondents are presented with a full-ticket match-up, Obama leads 45% to 42%. The poll was conducted Sunday through Wednesday.
  • Obama leads 48% to 46% in an ARG poll of Michigan. He leads among independents but is relatively weak among Democrats.
  • McCain leads 47% to 45% in a Miami Herald poll of Florida. It was conducted Sunday through Wednesday. Obama has a 9% edge on the economy. McCain gets 17% of former Clinton supporters.
  • McCain leads 48% to 42% in a Ohio News Organization of Ohio. The poll is somewhat dated - it was taken the 12th to the 16th. 19% of independents are undecided.
  • The candidates are tied at 46% in PPPs poll from North Carolina. Bob Barr gets 5%. Only once before had there been a tie in North Carolina (Rasmussen’s April survey). 58% of respondents rate the economy as their biggest concern. The poll was conducted from the 17th to the 19th.
  • Obama leads 53% to 39% in a Research 2000 poll of Iowa. Obama leads by 18% among independents.
  • McCain leads 49% to 45% in a Research 2000 poll of Missouri. In the July poll, Obama led by 5% - but that was somewhat of an outlier.
  • McCain leads 53% to 40% in a Research 2000 poll of North Dakota. He led by only 3% in July.
  • Obama leads only 50% to 46% in a Rasmussen poll of Maine. There is no breakdown by district, but if Obama cannot win statewide by a larger margin he would be in danger of losing the first district’s EV.
  • McCain leads 51% to 45% in a Rasmussen poll of South Carolina, a surprisingly close result.
  • Obama leads 54% to 43% in an ARG poll of Connecticut.
  • Obama leads 54% to 39% in an ARG poll of Maryland.
  • McCain leads 59% to 36% in an ARG poll of Tennessee. Obama gets 27% of the white vote.

Meanwhile, in down-the-ballot polls:

  • Kay Hagan leads Elizabeth Dole 46% to 41% in PPPs poll of North Carolina’s Senate race. She led by 1% last week.
  • Chris Shays and Jim Himes are tied at 45% in an internal poll for the Himes campaign in CT-04.
  • Sam Graves leads Kay Barnes 51% to 42% in a SUSA poll of MO-06.
  • Jim Risch leads Larry LaRocco 56% to 33% in a Research 2000 poll of Idaho’s Senate race, a clear improvement over his 10% lead in July.
  • Lindsay Graham leads 50% to 41% in a Rasmussen poll of South Carolina’s Senate race. This was accompanied by an improbably tight presidential survey, so take the tightness here with a grain of salt as well.

This is the second time Hagan is posting a 5% lead, testifying to how unpredictable that Senate race has become given that other surveys are still showing Dole ahead. This is a race in which the presidential coattails will play a crucial factor. It’s unlikely Hagan can win if McCain wins in a blowout, but she would look very strong if Obama is within 2-3% of McCain.

Today’s polls also find more worrisome news for down-the-ballot Democrats, starting with Graves’ expanding his lead in MO-06, in what is one of the Democrats’ most coveted seats. We have seen this trend for a few weeks now: Democrats are not improving their position in the second-and-third tier races, the ones that would transform a strong congressional night into an amazing one.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Obama leads in IA, PA, MI while IN remains very tight; Dems lead in AK-AL and CO-04

Another day of strong polling results for Obama - this time at the state level. SUSA confirms that the Illinois Senator can feel more confident about Iowa than about many Kerry states, Marist finds larger leads than we have seen lately for Obama in the crucial states of Michigan and Pennsylvania (two states that are quasi-must wins for Obama) and two surveys from Indiana find the race within the margin of error. Who knew the Hoosier State would be polled so much?

What is fascinating about the Marist polls is that the surveys were taken over the week-end (thus before the financial crisis exploded) in Ohio and Pennsylvania, and at the beginning of this week in Michigan. The share of voters who say that they are most concerned about the economy is far greater in the Michigan poll (51%), which explains why Obama has such a large lead and confirms that the dominance of economic issues this week is helping fuel Obama’s comeback. Here’s the full roundup of today’s polls:

  • First, the trackings, where the movement is less uniform than it was yesterday: Obama gains one in Research 2000 (leads 49% to 42%) and in Gallup (leads 49% to 44%). Rasmussen doesn’t move (tied at 48%) and McCain gains 3% in Diego Hotline (but still trails 45% to 44%).
  • Obama leads 47% to 45% in a Marist poll of Ohio. The two are tied among registered voters. Those who say that the economy is the most important issue for them vote Obama by 14%. Obama gets 90% of Democrats. This poll was taken Thursday through Sunday.
  • Obama leads 49% to 44% in a Marist poll of Pennsylvania. The margin is 3% among registered voters. Obama gets 87% of Democrats and leads among independents. This poll was taken Thursday through Sunday.
  • Obama leads 52% to 43% in a Marist poll of Michigan. The margin is the same among registered voters. Obama gets 92% of Democrats, leads by 14% among those who say the economy is the most pressing issue. This poll was taken Tuesday and Wednesday, after the Wall Street collapse.
  • McCain leads 49% to 47% in a Rasmussen poll of Indiana. He led by 6% in August.
  • McCain leads 47% to 44% in an ARG poll of Indiana.
  • Obama leads 54% to 43% in a SUSA poll of Iowa. He gets 89% of Democrats and leads by 11% among independents. Among voters who are sure of their vote, he leads by 15%.
  • McCain leads 53% to 42% in an ARG poll of North Dakota.
  • Obama leads 50% to 44% in an ARG poll of Washington.
  • McCain leads Obama 64% to 31% in a SUSA poll of Alabama.
  • McCain leads 61% to 34% in an ARG poll of Oklahoma.

There is good news for McCain as well in this batch of surveys, most notably his strong margin in North Dakota (a state Obama has been contesting). A Rasmussen poll last week had found McCain jumping to a strong lead there after struggling through the summer. Republicans will also be satisfied to see that Obama is struggling in yet another poll from Washington - confirming that the Northwestern state is far less safe than people thought a few weeks ago.

Meanwhile, in down-ballot:

  • Betsy Markey leads Rep. Marilyn Musgrave 47% to 38% in a Grove Insight poll for Emily’s List of CO-04.
  • Andy Harris and Frank Kratovil are tied at 36% in a DCCC poll of MD-01.
  • Mark Begich leads Ted Stevens 50% to 44% in a Research 2000 poll of Alaska’s Senate race.
  • Susan Collins leads 55% to 42% in a Rasmussen poll of Maine’s Senate race.
  • Mitch Daniels leads Long Thompson 56% to 40% in a Rasmussen poll of Indiana’s gubernatorial race.
  • Daniels leads Long Thompson 46% to 42% in a Selzer poll of that same race.
  • Dino Rossi inches ahead 48% to 47% against Gregoire in a Strategic Vision poll of Washington’s gubernatorial race.
  • Lautenberg leads 49% to 42% in a Rasmussen poll of New Jersey’s Senate race.
  • Chambliss leads 52% to 33% in an internal poll conducted for his campaign in Georgia’s Senate race.
  • Inhofe leads 55% to 39% in a Rasmussen poll of Oklahoma’s Senate race.

The House races bring some excellent news for Democrats. Musgrave and Young are among the most vulnerable Republican incumbents, and those are not isolated polls. The CO-04 survey, for instance, confirms what SUSA found a few weeks ago. Democrats have been trying to kick Musgrave out for a few cycles, and it looks like this could be their year. As for MD-01, it has a very high percentage of undecideds, and in a heavily conservative district they are more likely to vote Republican. But it remains remarkable that Democrats are competitive in a district the GOP should be safe in.

As for the Senate races, Democrats will be satisfied that Begich is holding on to a lead, though the race is undoutedly much tighter than they would like it to be. There isn’t much else for the DSCC to get excited about here. Tom Allen, Bruce Lunsford, Jim Inhofe and Jim Martin are making little to no inroads in their respective Senate races, making it increasingly unlikely that Democrats will be able to contest more than the 9 races they have already put in play.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Both parties have results to celebrate

After two weeks of relatively few state polls, the pace has undoubtedly quickened and should continue to do so over the next two months. Given that the race is close, that means that both parties should have numbers to celebrate in each day’s polling wave, and today is a clear sign of that. With all eyes on NC after yesterday’s disastrous (but suspicious) SUSA poll, two new surveys from the state find the race remaining very tight; Obama can also be comforted by CNN surveys finding him ahead outside of the MoE in NH and MI, and by a curious poll finding a tighter-than-expected margin in WV. All these polls from crucial states were taken in the aftermath of the GOP convention but find little evidence of a McCain bounce.

But McCain has some good numbers as well, including a (narrow) lead in the crucial state of New Mexico, where most recent polls were finding Obama up by large margins, and surges in ND (where yesterday’s . He also posts leads outside of the MoE in MO and VA and gets dangerously close in Pennsylvania. Except for NM and ND (both polled by Rasmussen), the numbers are in line what we have been seeing through the summer and here again there is little post-convention shift at the level of the key battlegrounds.

Before going on to the full rundown, it is important to point out once again that McCain does seem to be enjoying a big bounce among independents. It’s now Fox News’s turn to find McCain jumping to a big lead in that group, and that happens because undecided independents made a choice rather than Obama bleeding support. In a sense, this should reassure Obama that the bounce certainly has the potential of fading - what group is more susceptible of changing its mind than independents who stopped being undecided in the immediate aftermath of a convention?

On to the long list of the day’s presidential polls, where Obama leads in every state won by Kerry in 2004 and McCain leads in every state won by Bush in 2004:

  • First, the trackings: Rasmussen finds the bounce fading, with Obama recapturing a small advantage, 48% to 47%; similarly, Diego-Hotline has the race back to a tie at 45% (the gender gap is shrinking on both sides, independents still favor McCain). Gallup, however, shows McCain’s lead holding at 5% for the third straight day, 48% to 43% - albeit the number of undecideds has slightly risen.
  • McCain leads 45% to 42% in a Fox News national poll taken Monday-Tuesday. This is largely due to a 16% bounce among independents. In August, indies broke 31-30 for Obama, now 46-31 for McCain. Also, independents are split when asked which ticket will bring more change to Washington, but a lot of them refuse to answer.
  • McCain leads 49% to 47% in the crucial state of New Mexico (polling history). This is McCain’s first lead in a Rasmussen poll. Obama led by 4% in August, 5% in July and 8% in June.
  • McCain leads 48% to 45% in another poll from North Carolina, an internal survey for the Perdue campaign. The survey’s partisan breakdown is 46% Dem, 35% Rep (that mirrors the actual numbers).
  • Obama leads 51% to 45% in a CNN poll of New Hampshire (polling history). This poll (like the 3 other CNN surveys listed below) was taken Sunday through Tuesday, in the aftermath of the GOP convention.
  • Obama leads 49% to 45% in a CNN poll of Michigan (polling history). A very worrisome sign for Obama, however, is that McCain leads by 18% in the Detroit suburbs that were the home of Reagan Democrats. Bush won those counties by 1%.
  • McCain leads 50% to 46% in a CNN poll of Virginia (polling history). This is his biggest lead since May… though it’s a narrow one. Very interestingly, Obama does much better than Kerry in the Norfolk area, but not in Northern Virginia - that’s obviously the region Obama needs to build up margins, and given the elections in 05 and 06 he is likely to do so.
  • McCain leads 55% to 41% in a Rasmussen poll of North Dakota. This is a big jump (they were tied in July), just as in Montana yesterday.
  • McCain leads 44% to 39% in a MBE poll of West Virginia. I have not heard of this group; the only other recent WV poll is a Rasmussen survey from early June that found McCain leading by 8%.
  • McCain leads 64% to 33% in Rasmussen’s first post-Palin poll from Alaska.

It is striking that the tightest numbers from a blue state come from Pennsylvania and not from Michigan and New Hampshire; it will be very interesting to see whether other surveys find a similar tightening in the Keystone State, and whether we are back to the familiar situation of PA looking more crucial than MI.

It will also be crucial to find out whether McCain can capitalize on his gains in North Dakota and New Mexico. The latter was moved in the lean Obama category in my latest ratings, and Democrats were hoping to feel relatively confident about that state and Iowa. While Virginia’s numbers are also troubling for Obama, they remain tight and two other polls released in the past two days find the race well within the MoE.

Finally, this leaves us with North Carolina. All polls have shown a 2-5% race for months now, and here two more polls find the same margin. The key difference with SUSA’s poll is the partisan breakdown. PPP and the Perdue poll have a large advantage for Democrats while SUSA had shown a massive shift towards the GOP for a 41-40 edge. But Democrats do actually dominate the state’s registration numbers: 45.3% of voters are registered Democrats, 32.7% are registered Republicans. If the GOP can over-perform, it would certainly be in a strong position but we will need to see more evidence of that.

Meanwhile, in down-the-ballot polls:

  • Three polls from North Carolina’s gubernatorial race. In the suspicious SUSA survey, Pat McCrory leads Beverly Perdue 49% to 41% - his first lead. In PPP’s latest poll, Perdue gets 41% to McCrory’s 40%. And in Perdue’s internal poll, she leads 46% to 40%.
  • Three polls as well from North Carolina’s Senate race (polling history). In SUSA, Dole retains an advantage, 48% to 40%. In PPP, Hagan is up 43% to 42%. (PPP’s previous survey released two weeks ago found Hagan leading by 3%.) In Perdue’s internal poll, Dole is up 48% to 46%.
  • In Alaska, yet another poll finds Ted Stevens climbing back (polling history). Rasmussen shows that he is within 2% of Mark Begich (48% to 46%) after trailing by 9% right before his indictment and 13% right after.
  • In New Mexico, Rasmussen continues to show tightening results in the Senate race. Tom Udall now leads Steve Pearce 51% to 44%. The 10% lead Rasmussen had found in mid-August was already considered a disappointing result for Udall.
  • In the Oklahoma Senate race, Jim Inhofe crushes Andrew Rice, 56% to 34%.
  • In Washington’s gubernatorial race, Dino Rossi has his first lead in many months in SUSA’s latest polling, 48% to 47%.
  • In PA-04, an internal poll for the Hart campaign shows the former Republican congresswoman trailing 49% to 44% against current Rep. Jason Altmire.

Here again, it is hard to know what to make of the NC polls, though we can probably agree that both the gubernatorial and senatorial races are presently too close to call. In Alaska, this is now the third poll to find a significant Stevens bounce, and it does look like that race is once again too close to call. But the result of that match-up is almost entirely dependent on Stevens’ trial, which will be starting shortly.

Also, PA-04 is rated toss-up in my latest House ratings, and for an incumbent to be under 50% is always sign of trouble (though less so when the challenger is a well-known former representative). New Mexico’s Senate also is showing interesting trendlines, though Rasmussen is the only pollster to find that Udall might not be as favored as he used to be. Remember that the NRSC looked to be pulling the plug on Pearce two weeks ago.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Polls: McCain gains 8% in CBS poll, Obama takes first lead in red ND but loses opening in AK

37 million viewers tuned in to watch Sarah Palin last night, almost as much as the 38 million that watched presidential nominee Barack Obama last week even though his speech was transmitted on four more networks. Palin has become a huge story, and whatever voters thought about her speech will surely have repercussions.

CBS just released a new national poll, and it finds quite a sharp change in just a few days: Obama was leading by 8% in a poll taken over the week-end, but the race is now a tie in a poll taken from Monday to Wednesday, suggesting that whatever bounce Obama got faded quickly - and before Palin even took the stage.67% of Clinton supporters now back Obama (58% last week) but McCain has a similar uptick among evangelicals (57% to 66%). Obama’s lead among female voters is smaller, 43% to 38%. Note that the previous poll was taken after the Palin pick, so this is a post-post VP and pre-convention bounce for the Republican.

However, the Gallup and Rasmussen trackings are showing little movement in their latest polls taken over the same period. Gallup has Obama leading 49% to 42% (he led by 6% yesterday), and Rasmussen has Obama leading 50% to 45% (same as yesterday). At this point last week, Obama had already posted gains in the tracking, but keep in mind that the Denver convention had a Monday night, but the GOP did not.

And another national poll, taken by Democracy Corps (a Dem. pollster) yet again in the Monday-Wednesday period, has Obama leading 49% to 44%. As usual, the pollster put a heavy focus on the 18 battleground states Obama has invested in (12 of which were carried by Bush in 2004), and there Obama is ahead 49% to 43%. That’s an impressive lead, it can partly be explained by the fact that Obama has big leads in some of the Kerry battleground states (MN, WI) but it clearly goes to show that the election is being waged in Republican terrain and Obama is still doing well.

For now, the Palin effect seems to be increased polarization. McCain is gaining among Republicans and the base is very excited - Rush Limbaugh has dropped all his animosity to the ticket and is now calling McCain “McBrilliant.” But the Obama campaign is saying that they raised $8 million offline since yesterday’s primetime ended, an outstanding sum that I believe exceeds the amount McCain raised last week in the 18 hours after the Palin announcement, a clear suggestion that the intensity of Democratic partisanship also shot up last night. Also, keep in mind that the McCain campaign can no longer raise money, as it now has to limit itself to $84 million (note that Republicans can still donate to the RNC, which raised $1 million since yesterday).

Let’s get to the day’s state and district-level polling:

  • In North Dakota, Obama has taken his first lead ever in a DFM Research poll conducted just before Obama’s acceptance speech. He is up 43% to 40%, within the margin of error.
  • In Alaska, the last poll had Obama leading by 5% but the first post-Palin survey has McCain jumping to a huge lead, 57% to 33% with Palin’s approval rating at 86%. However, this is a poll that is being circulated by the McCain campaign (though the campaign claims it did not commission it); it is extremely rare for a presidential campaign to leak an internal poll, so this just goes to confirm how eager they are to highlight Palin’s appeal among voters who know her.
  • Democrats got some bad news in MO-09, a district they are contesting. SUSA found Republican Blaine Luetkemeyer leading Judy Baker 50% to 38%. Obama was crushed 60% to 36%, numbers that are much worse than Kerry’s in 2004.
  • In KY-02, however, a Democratic internal poll suggests an opportunity for Dems to take a very conservative district (even though the district’s partisan ID is 58% Democratic, it voted for Bush with 65%). The poll shows Democratic state Senator Boswell leading fellow state Senator Brett Guthrie 41% to 33%.

Alaska, Montana and North Dakota are the three extremely Republican 3-electoral vote states that the Obama campaign has been airing ads in over the past 2 months. In the first two, at least one poll had shown Obama taking a stunning lead some time in the summer (see Montana’s polling history and Alaska’s polling history). Now, Obama seems to be making progress in North Dakota. The prior two polls (taken by two different institutes) showed McCain only by 1% and 3%, but seeing a Democratic presidential candidate leading by any margin here is truly remarkable.

3 electoral votes might seem negligible compared to the high stakes of Ohio and Michigan, but keep in mind that if the election is close we are talking about very small margins in the electoral college. McCain can certainly not afford to give up on either North Dakota or Montana, and even if there is no other benefit to the Palin pick, it is significant that she anchored Alaska’s 3 votes in the Republican column. As I said, the last poll had Obama leading by 5%. While we will be looking for independent polling that does not come from the McCain campaign to confirm this survey, I had already moved Alaska out of the toss-up column in my latest “veepstakes special edition” presidential ratings.

MO-09 and KY-02 are comparable in the sense that they are both deeply conservative open seats in which Democrats usually stand no chance. Both have been polled over the summer, and it is interesting to compare the results. An independent (SUSA) poll from KY-02 in early July found Boswell up by 3%, suggesting that the internal poll is not completly out of line. An internal poll for Baker in MO-09, however, found her leading by 2% just two weeks ago. Losing these districts would be devastating for the GOP and would mean that Democrats have a shot at a big wave like 2006; we will know more about whether (or rather where) Democrats are the most competitive by looking at the party’s expenditures over the next 2 months.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Fifth presidential ratings: Florida’s first move

As the presidential race started to fall into place and we started getting a better idea of which candidate had the advantage in the key battleground states, the number of toss-up electoral votes shrank in each installment. Today, Michigan and Florida migrate back to the toss-up column, bringing it back up to 100 electoral votes - the highest since June 4th. In fact, this is Florida’s first move out of the “lean McCain” category. This might not be the wisest of moves given that Quinnipiac’s poll of the “Big Three” (FL, PA and OH) will be released in just a few hours and could very well contradict me, but it is Wednesday night so I cannot delay my presidential ratings any longer.

With 8 states with 100 electoral votes considered up for grabs, the election remains wide open - and the latest national polls showing a tight race attest to that. At the same time, this does not mean that the eletion is a toss-up. In fact, Obama’s advantage is the biggest it has been and now stands at 38 electoral votes. To make matters worse for the Republican, his base keeps eroding - a phenomenon we have seen week after week. Only 200 electoral votes are now rated in McCain’s column and his base (safe+likely) has also reached an all-time low of 165.

Soon, the two candidates will announce their vice-presidential picks and that alone is likely to provoke some changes in the ratings. Not all potential picks would transform the electoral equations in their state, but Richardson, Bayh, Crist or Pawlenty picks could lead to some changes in their respective states - at least temporarily. I am still not convinced Mitt Romney would have as dramatic an impact in Michigan as some say he would, but that could be another question mark we will have to keep an eye on.

Furthermore, it has now been quite a while that the Obama campaign has been running advertisements in staunchly red states that McCain has been ignoring (North Carolina is the main one, but also North Dakota, Montana, Alaska, Indiana and Georgia), allowing Obama to get his message out in a vacuum - the best situation for a politician to be in. For now, I have rated none of these states as a toss-up, but it goes without saying that McCain could soon have more to fear in those states than in states like Virginia and Colorado where he is playing defense. He might either have to invest his own resources here (divesting them from places like NM and CO) or a number of these states could move to the toss-up column.

Without further delay, here are the fourth 2008 electoral college ratings (states whose ratings have been changed are in bold). Remember that states that are in the “lean” category are still considered to be very competitive and certain to be hotly contested, but it is possible to say that one candidate has a slight edge at this time.

  • Safe McCain: Alabama, Arkansas, Idaho, Kansas, Kentucky, Louisiana, Mississippi, Nebraska (at large + 3rd congressional district), Oklahoma, South Carolina, Utah, Tennessee, West Virginia, Wyoming (90 EVs)
  • Likely McCain: Arizona, Georgia, Indiana, Nebraska (1st and 2nd congressional districts), South Dakota, Texas (75 EVs)
  • Lean McCain: Alaska, Montana, Missouri, North Carolina, North Dakota (35 EVs)
  • Toss-up: Colorado, Florida, Michigan, Nevada, New Hampshire, New Mexico, Ohio, Virginia (100 EV)
  • Lean Obama: Iowa, Oregon, Pennsylvania, Wisconsin (45 EVs)
  • Likely Obama: Delaware, Maine (at-large, 2nd district), Minnesota, New Jersey, Washington (42 EVs)
  • Safe Obama: California, Connecticut, DC, Hawaii, Illinois, Maine’s 1st district, Maryland, Massachusetts, New York, Rhode Island, Vermont (151 EVs)

This gives us the following map and totals:

  • Safe + Likely Obama: 193 electoral votes
  • Safe + Likely + Lean Obama: 238
  • Toss-up: 100
  • Safe + Likely + Lean McCain: 200
  • Safe + Likely McCain: 165

I will naturally not attempt to provide an explanation for every single one of these ratings and will concentrate instead on those that have shifted over the past two weeks:

Florida, lean McCain to toss-up: Throughout the spring, Florida was widely considered like the one battleground state from the past 2 cycles that started off in the McCain column and one state in which Hillary Clinton would have performed stronger than Obama. Over the past few weeks, however, a combination of factors have led Florida to rejoin the group of toss-ups. First, polls have shown is back to being a toss-up. These ratings are not determined by a compilation of the latest polls, but it is impossible not to take into account all 3 polls released in July (ARG, PPP and Rasmussen) have found Obama ahead within the margin of error. That is a progression from this spring, when Obama was routinely crushed by McCain in polls from this state (see Pollster.com’s graph).

Second, Obama is undoubtedly benefiting from the superior Democratic organization over the past few months. Since the beginning of the year alone, new Democratic voting registrations have outpaced Republican ones 7:1 for an advantage of almost 100,000 voters… Groups are working hard to register former felons, whose voting rights are being restored. Furthermore, the Obama campaign is working hard at organizing in the state, contradicting some suggestions that they might be looking to pass on the Sunshine State. They already have 16 offices in the state, far ahead of where Gore and Kerry were at this stage in 2000 and 2004.

Finally, Obama is stronger among key Florida constituencies than Democrats previously feared. He does not look to be suffering from any sort of problem with Hispanic voters. His weakness among Latinos in the Democratic primaries combined with McCain’s relatively moderate profile on immigration led some to speculate McCain might score gains in that constituency, but poll after poll have shown Obama crushing McCain among Hispanics nationally by a bigger margin than in 2004. In Florida, Republicans are stronger among Hispanics because of the Cuban vote but McCain’s hopes to improve on Bush’s showing seems to be illusory. Another group among which Obama might not have quite as big a disadvantage as thought is Jewish voters - an important constituency in Florida. It looks like McCain is having his own problems with Jewish outreach.

Michigan, lean Obama to toss-up: Michigan stayed in the Obama column for only two weeks, with two changes in back-to-back ratings. I confess I might have been driven by polls more than I wanted to in my previous ratings: Rasmussen, Quinnipiac and PPP had all showed Obama opening a larger lead and that seemed to fit with Obama’s gains in other blue states like Wisconsin and Minnesota. However, polls over the past week have shown tighter races, with Quinnipiac and PPP both scaling back their findings to Obama leads within the margin of error. EPIC-MRA - the most reputable pollster in the state - also found a 2% race.

It has long looked that the McCain camp is intent on replacing Pennsylvania with Michigan as the large blue state it will contest the most strongly. The past few week shave shown very little to contradict that, with the McCain campaign concentrating ad buys, media campaigns and field organization on Michigan to an extent that was not seen by the Bush campaign in 2000 and 2004. In fact, the amount of buzz Mitt Romney is getting in the GOP veepstakes seems mainly driven by the belief in Republican circles (as summarized by Bob Novak last week) that Romney would make his ticket much stronger in Michigan. There is only so much money the McCain campaign can spend on the offensive and so it is likely to concentrate its money hitting only a few Kerry states - reserving the rest for the defense of the many endangered red states.

Michigan is likely to get a large share of whatever budget the GOP has to play offense, and that alone should guarantee that this state remains tight.

North Dakota, likely McCain to lean McCain: North Dakota thus joins Alaska and Montana as staunchly red states that have somehow found themselves competitive. The most recent ratings were devoted to the battle of the Mountain West. Just as in Montana (and Alaska, which is not the Mountain West but is part of the same type of strategic consideration), it is not just that Obama is polling much stronger than expected but he is actually airing ads in the state and backing that up with visits. Since my previous ratings, a Research 2000 poll came to confirm Rasmussen’s earlier finding of a tight race, and that corroboration is enough for me to take North Dakota to the next stage.

Special note on Indiana and New Hampshire: Some commentators protested some of my ratings two weeks ago, most notably those in Indiana and New Hampshire. In the latter state, McCain’s two primary victories were won not because of the GOP vote but because of independents; in fact, a surprising number of independents chose to vote for McCain rather than Obama (the only time during the primary season the two candidates were competing over the same voters), costing the Democrat a victory against Clinton. In the past two weeks, 2 out of 3 polls have found the race within the margin of error.

As for Indiana, it is true that Obama is running advertisements in the state and that is leading me to seriously consider moving the state to lean Republican. In fact, Georgia and Indiana are the only two states among the 18 the Obama campaign is contesting that are rated likely or safe Republican. Simply put, the state’s heavily Republican bent (Bush won by 21% in 2004) is keeping me from moving the state towards a more competitive category. It is true that I am now rating ND, AK and MT (all staunchly red states) as lean McCain; but there is now a number of polls from each of these states showing consistently tight races. On the other hand, there is very little information coming out of Indiana. A poll in June found Obama up by 1%, yes, but it was also the only poll from the state released in the past two months.

History of Campaign Diaries’ electoral ratings:

  • July 30th: + 38 Obama (238 for Obama [151 safe, 42 likely, 46 lean] and 200 for McCain [90 safe, 75 likely, 35 lean]
  • July 16th: +28 Obama (255 for Obama [150 safe, 43 likely, 62 lean] and 227 for McCain [90 safe, 78 likely, 59 lean]
  • July 2rd: +11 Obama (238 for Obama [143 safe, 50 likely, 45 lean] and 227 for McCain [93 safe, 78 likely, 56 lean])
  • June 18th: +22 Obama (238 for Obama [86 safe, 97 likely, 55 lean] and 216 for McCain [87 safe, 87 likely, 42 lean])
  • June 4th: +20 McCain (207 for Obama [76 base, 107 likely, 24 lean] and 227 for McCain [97 safe, 77 likely, 53 lean])

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Obama’s campaign aims to go national and has clear organization edge

Two narratives have somewhat paradoxically collided in these early weeks of this presidential election. On the one hand, the shifts in partisan identification and Barack Obama’s determination to change the electoral map have significantly eroded John McCain’s base. On the other hand, states that were battlegrounds in 2004 have remained very tight, ensuring that McCain remains highly competitive in the presidential election.

This morning, we had a taste of the latter storyline as 5 polls from crucial swing states showed narrow races. Other developments today highlight the first storyline and the unprecedented national scope of Obama’s campaign. As the Democrat started running ads in states like North Dakota and Indiana last month, we got out first sense that talk of expanding the map was not just a faint. An analysis of Obama’s campaign organization published today by The Hill confirms that Democrats are serious about contesting these states.

Obama has already opened 4 campaign offices in Alaska and 6 in Montana. McCain has no offices in either of these red states. This is a repeat of the primary scenario: Obama’s organized in the caucus states Clinton ignored (Colorado, Alaska, Idaho), gaining a decisive edge in the delegate race. The stakes in the presidential race are different, of course, since electoral votes are not allocated proportionally. But given that no Democratic presidential candidates have opened campaign offices in Alaska or Montana in decades, the mere act of organizing troops in those states could have a dramatic effect on November results. In fact, two polls from red states released this afternoon by Research 2000 confirm that McCain has a lot to worry about:

  • In Mississippi, McCain leads 51% to 42% - versus a 15% lead in May. Obama gets 19% of the white vote. He will need to improve that share a bit as well as boost black turnout. (The poll is made up of 37% of African-American respondents versus 35% in 2004.) One positive note for Obama: 15% of the poll’s black respondents are undecided versus 3% of white respondents. He has room to grow. (As a reminder: I have been skeptical of Obama’s chances in Mississippi.)
  • In North Dakota, this is the second poll in a row (after Rasmussen’s) to find a toss-up, with McCain up 45% to 42% within the margin of error. This is a state Obama is actively competing in.

As if to confirm its intent to fundamentally alter the rules of the game, the Obama campaign finalized the first national advertisement buy by a presidential campaign since 1996. That year, Bob Dole aired a single national ad. This year, Obama has bought an expensive $5 million package of spots to be aired during the Olympics. In an age in which presidential election play out on a select number of battlegrounds, campaigns do not see the utility of buying time nationally on broadcast television for they are then paying to have their ad seen by voters in Rhode Island and Wyoming, Kansas and Illinois, New York and California - none of them states that Obama and McCain are preparing to contest.

Some will say that the Obama campaign is wasting its resources. Why spend anything on Montana when it is much more important to win Colorado, Iowa and New Mexico and thus get to 273 electoral votes - whatever the popular vote margin? Three days ago, I explained that Obama’s gambit is very much a win-win move: Either McCain does not respond and opens no offices, runs no ads in MT, AK and NC and Obama’s chances in those states risk becoming even better than in Virginia and Colorado; or McCain responds and divests his limited resources away from states like Virginia and Colorado, leaving those more vulnerable.

It looks like there already are signs that the unlikely erosion of the GOP electoral base is forcing McCain to divest his time and money - a victory for Obama. McCain has been campaigning in… Arizona this month, staging campaign events and directing his staff to pay attention to the state. This is startling given that Arizona is a lean Republican state to start with and it is McCain’s home state. There have been hints for a while that Arizona could be closer than expected, but keep in mind that this isn’t even one of the states Obama has been investing in.

And keep in mind that the Obama campaign has subtantially more resources, so that it can spend in Alaska and Montana while also heavily investing in the more traditional battleground states. In fact, The Hill’s article emphasizes just how big an organizational edge Obama is gaining in states in which McCain is supposedly concentrating in: By the end of the week, Obama will have 18 offices in Ohio and 20 in Virginia, compared to 8 and 6 for the McCain campaign! In Missouri, Obama is planning on sending 150 paid staffers and has 50 presently; McCain is described by The Hill as only having “a handful” and planning for 50.

These organizational descrepencies will have a very concrete effect come Election Day: They will impact voter registration, turnout and enthusiasm. These factors might not be determining in blow-out elections, but in close campaigns they can easily account for the 1% to 2% differential that could have gotten Al Gore and John Kerry in the White House. In 2004, the Kerry turnout operation in Ohio ended up being swamped by Bush’s, and that alone appears to have swung the election towards the Republican.



If you like the website...

... Support Campaign Diaries


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Recent Posts


    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • All good things must come to an end

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What remains on the table

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Confusion in Connecticut (Updated)

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Results thread, part 2: Dems suffer staggering losses in House and legislatives races, limit damage in statewide races

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election Night results thread: Rep. Boucher’s fall first surprise of the night

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election night cheat sheet

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Final ratings: Democrats brace for historic losses

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What to watch for down-ballot

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archives