Slashdot Mirror
DuckDuckGo - Is Google Playing Fair?
Penurious Penguin writes "Privacy-oriented search-engine and Google-rival DuckDuckGo is contending possible anti-competitiveness on the part of Google. MIT graduate and founder of DuckDuckGo Gabriel Weinberg cites several examples; his company's disadvantages in the Android mobile OS; and browsers, which in Firefox requires only a single step to set DuckDuckGo as the default search — while doing so in Chrome requires five. Weinberg also questions the domain duck.com, which he offered to purchase before it was acquired by Google. His offer was declined and duck.com now directs to Google's homepage.
Weinberg isn't the first to make similar claims; there was scroogle.org, which earlier this year, permanently shut down after repeated compatibility issues with Google's algorithms. Whatever the legitimacy of these claims, there certainly seems a growing market for people interested in privacy and objective searches — avoiding profiled search-results, a.k.a. 'filter bubbles.'"
It's all about numbers, shares, dollars and control of data.
What seems more likely:
1) He offered to buy duck.com from On2 Technologies (which was originally named The Duck Corporation), but they held out for more than he was willing to offer. It's an obviously valuable domain name so this doesn't require some kind of secret agreement with Google: maybe they just thought they could get more than he was offering for it.
2) Sometime later, Google bought On2 for their codec (VP8, on which WebM was based). Of course this means they got all their other assets too, like their old domain name. Typical Google practice is to redirect acquired domain names to google.com, or to a specific product page on google.com if relevant. Considering that Google is very interested in codecs, it seems rather unlikely that Google really bought On2 for the domain name.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
They didn't specifically purchase duck.com, though. They bought On2 Technologies, formerly known as The Duck Corporation, in order to acquire the VP8 codec, which became WebM, and got all the rest of On2's assets as part of the package. It seems unlikely that the real point of the purchase was to acquire duck.com, considering that VP8 is actually pretty important to them.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
I started working at The Duck Corporation (duck.com) in 1996, a few years before it went public as On2 Technologies/The Duck Corporation (on2.com and duck.com), and was working with Google/Duck/On2 until a year and a few months after the acquisition in 2010. At Duck/On2, I was responsibile for everything related to building our networks and maintaining all the hardware, software, servers, domains, networks and a ton of other stuff, you know the typical system administrator job.
Prior to the acquisition, but after going public as On2, we likely didn't sell duck.com because that was still my primary email address and I and a few others still actively used it, and we still kept up a basic website for information about our old and basically no longer supported software; and it was just one of those things still tied to the company with a lot of history as The Duck Corporation, so we decided to keep it. Feel free to blame me, since I always requested that we keep it when we saw the many offers for the domain over the years, mostly in the hundreds to couple of thousand dollar range; and because of my history with the company, I am sure I was a big part of that decision to not sell it.
When Google bought us, I knew I was still going to be there for a while to make sure all our company data, and some specific services that had to stay up, was migrated into their servers. Since we hosted all our own servers with our own hardware and software and they had to ulimately be shut down, I had to get things moved over and still needed to get my duck.com email.
So at that point, since I was still getting a lot of duck.com emails and had my duck.com email address for literally many hundreds of websites, publications, mailing lists, business contacts and other things, since I mainly used duck.com for well over a decade, I wanted to make sure Google's DNS and email was configured to still get duck.com emails. I actually had started trying to switch all my duck.com to google.com, but it was an overwhelming process. I still wonder how much email is still going to my duck.com email address.
I took it upon myself to learn the Google way of configuring their public DNS, email and a bunch of other things because I was nosey and wanted to learn and did learn some really cool and interesting stuff about them while I was there. I made sure the MX record for duck.com was still configured to deliver my email (and a few other email addresses) to my Google email account. Since it was decided to no longer keep the website up, I can't give you a real explanation, but I ended up configuring duck.com websites to point to the google.com main page instead of nothing. So you can go ahead and blame me, but no one at Google specifically told me to point duck.com to their site.