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

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
San Diego Serenade » Feedback from the Reader

San Diego Serenade



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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32

Feedback from the Reader

Posted in San Diego by Conor on the
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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
August 23rd, 2006

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 250

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 250

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 241

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 232

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 250

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 241

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 232

The next issue of the Reader has come out, and it published no less than six letters to the editor regarding my Cover Story. It was obviously a divisive article, and thanks to their comments, several San Diego residents have earned themselves a spot on my Richard Nixon style enemies list. Brian “Absolutely horrible…what a moron” Nelson, Shannon “how much of an idiot your writer is” Riccio and Mariah “monotonous and dragging” Burzynski, welcome to the club!

I think it’s really great that the San Diego Reader is willing to print the opinions of its readers, and my three new enemies should be proud that their thoughts were published. To tell you the truth, there’s only one real difference between the Reader printing Brian Nelson’s, Shannon Riccio’s, and Mariah Burzynski’s opinion and them publishing mine:

1000-dollar-billz.jpg

One of us got One Thousand Dollars for their opinion.

One thing that I did find interesting was that no matter whether people thought the article was poorly written by a moron or hitting things dead center, nobody stood up for the radio stations. Nothing from an employee, or even an impassioned fan. Where are all those people?

3 Responses to 'Feedback from the Reader'

Subscribe to comments with RSS


  1. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_author_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Deprecated: Function ereg() is deprecated in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 263

    Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 266

    Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 268
    cat dirt said,

    on
    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    August 24th, 2006 at
    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    8:13 am


    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 256

    you need to be FIRED IMMEDIATELY from the READER!!!
    that was my favorite letter.


  2. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_author_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Deprecated: Function ereg() is deprecated in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 263

    Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 266

    Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 268
    bob said,

    on
    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    August 24th, 2006 at
    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    4:30 pm


    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 256

    I read your article in the reader over lunch. I thought it was outstanding…nothing is as divisive as music and it took some guts to be honest as you were.

    Trust me, it did more GOOD than harm..anytime we can expose the vapidness of radio and the local music scene here in SD at large we must take full advantage.


  3. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_author_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Deprecated: Function ereg() is deprecated in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 263
    Rich said,

    on
    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    August 24th, 2006 at
    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    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/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    6:54 pm


    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 256

    Ha! That $1000 comment made me laugh so hard that I peed a little.

Leave a Reply



Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1329

Strict Standards: Non-static method GA_Filter::spool_this() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 180