Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the podcast-player domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/birdseye/public_html/wp-includes/functions.php on line 6121
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":6527,"date":"2016-07-10T10:11:42","date_gmt":"2016-07-10T15:11:42","guid":{"rendered":"http:\/\/www.birdseyeviewbaltimore.com\/?p=6527"},"modified":"2016-07-10T10:16:30","modified_gmt":"2016-07-10T15:16:30","slug":"2016-bevys-ice-floe-award","status":"publish","type":"post","link":"https:\/\/www.birdseyeviewbaltimore.com\/2016-bevys-ice-floe-award\/","title":{"rendered":"2016 BEVys: Ice Floe Award"},"content":{"rendered":"It\u2019s that time again: the 2016 BEVys are almost upon us. We have so many great awards presented by our friends and colleagues in the Bird-O\u2019s-Sphere, but we have a couple of our own we would like to bring you.<\/p>\n
<\/p>\n
Ice Floe Award<\/h1>\n
We finally did it! We finally ran Brian Matusz out of town on a rail! Or, as I have been saying for a couple of seasons, we needed to put him on an ice floe and push.<\/p>\n
So.<\/p>\n
Mission accomplished.\u00a0OR IS IT?!?!<\/strong> Now that we know we have this power (because the Orioles finally cutting ties with an under performing player was totally affected by our whim as fans, right?), who should be the next player sent out on an ice floe, and pushed into the great DFA in the sky?<\/p>\nYou can vote on Twitter, and help us decide:<\/p>\n
<\/p>\n