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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/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 'EDT/-4.0/DST' instead in
/homepages/5/d194325218/htdocs/doyleforcongress/wp-includes/functions.php on line
55
FCC report finds community radio doesn’t hurt commercial stations
Strict Standards: Non-static method nggallery::get_option() should not be called statically in
/homepages/5/d194325218/htdocs/doyleforcongress/wp-content/plugins/nextgen-gallery/nggfunctions.php on line
10
January 5, 2012
The Hill Hillicon-Valley Blog
A Federal Communications Commission (FCC) report released Thursday found small, community radio stations do not impact the ratings or revenue of large commercial stations.
“Our final conclusion is that the analysis finds no statistically reliable evidence that [low-power FM] stations have a consistent effect on the economic performance of full-service commercial FM stations,” the report found.
The Local Community Radio Act, signed by President Obama last year, repealed restrictions on low-power FM stations, or LPFMs. The law required the FCC to study whether additional community stations hurt large stations.
“The study confirmed the widespread belief that LPFMs don’t cause economic harm or interference to other stations,” said Rep. Mike Doyle (D-Pa.), who sponsored the Local Community Radio Act. “In fact, if you talk to the folks in the regions that already have LPFM stations, they say LPFMs have had a very positive impact. They provide programs that reflect and enrich local cultures.”
http://thehill.com/blogs/hillicon-valley/technology/202605-fcc-report-finds-community-radio-doesnt-hurt-commercial-stations
