Visiting Ghent (in Belgium) one time, Google maps told me to cross a bridge that didn't exist to get from the train station to my hotel. I did consider swimming, but instead spent 30minutes walk along the river to the next bridge.
Posted
by
CmdrTaco
from the step-in-the-right-direction dept.
KirinMercury writes "Google began offering an encrypted option for Web searchers on Friday and said it planned to roll it out for all of its services eventually. People who want to use the more secure search option can type 'https://www.google.com' into their browser, scrambling the connection so the words and phrases they search on, and the results that Google displays, will be protected from interception." Note that you need the 'www' for it to work. Dropping it redirects you to a non-ssl page. You might have read this on Saturday, but if you missed it, it's still worth knowing.
I've always been a big fan of releasing my academic work under a BSD licence. My work is funded by the taxpayers, so I think the taxpayers should be able to do what they like with my software.
So I fully agree that all software should be released. It is not always enough to just publish a paper, but you should release your code so others can fully review the accuracy of your work.
This is the second time. On the first Google DNS article, and now here. I'm just trying to drive traffic to my blog. Don't worry, this time it seems to have worked so I'll stop my shameless advertising:)
I ran my own set of experiments benchmarking both Google DNS and OpenDNS as well as two UK ISPs. I showed more detailed results, and infer some information about how these systems are run.
http://bramp.net/blog/google-dns-benchmarked
I ran some tests against Google DNS and some other DNS providers to measure if Google DNS was actually faster than say OpenDNS, or my local ISP.
The results showed OpenDNS completely outperformed Google, but Google did do better than two local ISPs.
Read my blog entry about this.