Google's initiative to put privacy and security back into the hands of users through a revised permission system has received generally positive responses. It's no secret that this approach closely matches the way iOS prompts users for access to things like the contacts or location. Aside from the possibility that permission requests could become annoying with too much frequency, this has proven to be a pretty effective approach. However, since the announcement, one sticking point seems to have emerged around access to the Internet.

Dear residents of Atlanta, Charlotte, Nashville, and Raleigh-Durham—I now hate you. I am not alone in my unremitting dislike of you. Indeed, most of the web now despises you and your upcoming access to the holy grail of internet access, Google Fiber. Yes, Google is rolling fiber out to these four metro areas in the coming months. Congratulations, jerks.

To the residents of Kansas City, Kansas and Kansas City, Missouri: we hate you. Sincerely, every Internet user in the United States.

We've known about Google's plan to roll out its very first fiber optical Internet and cable service in the twin Midwestern cities for months, but today the full scope of Google's plans has been revealed on the fiber.google.com page. The options are staggering, the technology is drool-inducing, and the extras are enough to make even Google I/O attendees jealous.

An interesting little tidbit came across to us in an otherwise ordinary posting on Amazon's app developers' blog. While developers will have the option to use DRM or not in their apps, those that do use the digital licensing service may present problems for those users who are temporarily without an internet connection.

Comparing it to the way Amazon currently handles the storing of Kindle books, the curious part of the post reads:

"Any app that has Amazon DRM applied to it will require users to have installed and signed-in to the Amazon Appstore client to access the app.