I love this, really. Now when doing DNS testing from any location I can always test using 8.8.8.8, that's a huge benefit to me.

However, They're telling end-users to "try" their DNS service and giving basic instructions.
Their geo-location is no-where near complete, for end-users in (for example) New Zealand who follow their instructions they'll have:

* Pro: A DNS Server that will most likely have nearly all results cached, quicker overall response.
* Pro: DNS Infrastructure redundency through Google.

But...
* Con: A DNS System with higher latency.
* Con: A DNS System where if using only those two servers (through Googles instructions) when International connectivity dies, so does all your DNS.

I've moved my home server over to 8.8.8.8, 8.8.4.4, ISPDNS1, ISPDNS2 to negate these issues and provide better DNS service than my ISP.
I honestly would have expected more from Google, at the very least a geo-location test to ensure they have DNS servers in your "region" before advising to "Try" their system.

The hint of what I thought could be 'slander' in the article made me "Google" the name. http://www.myspace.com/michelle_i_sullivan - turns out it's not slander.

I'm having a BBQ next weekend, what kinds of meat are they offering?

At: http://news.slashdot.org/palm

In so many ways this interface is all it needs to be for 'read only' access to slashdot.
- Most recent articles: Check.
- Article with relevent links: Check.
- Top five comments (as moderated): Check.

It could be considered over-simplification, but over-simplification may be the best alternative to over-engineering.

I put this script together a while back to help me relive the days of quality slashdot content.

curl --silent http://feeds.digg.com/digg/container/technology/popular.rss http://feeds.digg.com/digg/container/science/popular.rss http://feeds.digg.com/digg/container/gaming/popular.rss | grep -e "<title>digg.com: Stories" -e "<link>http://feeds.digg.com" | sed -e '/<title>digg.com/shttps://f6ffb3fa-34ce-43c1-939d-77e64deb3c0c.atarimworker.io/g' -e '/<\/title>/s///g' -e '/<link>/s///g' -e '/<\/link>/s///g'

Yes, I'm kidding, Yes, it works.