Late last week we received a very terse email from Google, notifying us that we would be denied entry to the Google I/O conference set for next week.
This was a complete surprise to PhoneNews.com, and we responded requesting reasons why we were being denied entry. To date, Google has not responded.
Our impartial policy across all our Newsroom Network family of sites, is to not cover an event that denies us entry as credentialed media. And, we are going to do that with Google I/O unless the winds change. But, we hope that you can help there.
We’d like you to politely contact Google I/O event management and remind them that PhoneNews.com is the biggest name in phone news (Google ‘phone news’ if you’re in doubt on that). Again, be polite and respectful, but just let them know that whatever reason they may have for not letting us in… isn’t going to help Google in the short run or the long run.
As usual, we do have stuff in reserve for when these type of things happen, we’re confident you’ll stay tuned to PhoneNews.com (and TechNews.biz) throughout Google I/O… even if we aren’t talking about it.
Part of being the most critical, hard-hitting member of the mobile media means talking about stuff companies don’t always like. But, positive companies don’t wind up as losers when we have to do that.
We realize partners sometimes don’t always agree (we are a proud partner of Google News, in case you didn’t know). And, we hope to partner with Google on future news ventures. This one may be beyond us, but Google like all large companies has lots of different people, and it’s always possible some of them haven’t heard of PhoneNews.com just yet.
Update: Google has responded after receiving an influx of emails from readers. Google claims they attempted to contact us back in February to confirm our credentials. After an exhaustive internal search, we cannot come up with any evidence that such contact was ever received.
Google now cites fire codes as being unable to seat us, claiming the event is full.
PhoneNews.com has responded to Google that it is unfortunate that they cannot accommodate us, but their lack of any buffers for these type of errors means we have no choice but to enforce our existing policy. We will not be covering any developments from Google I/O, and will compensate for that with exclusive content during those days.