Getting it Wrong
For quite some time, Google (which runs on upwards of 10,000 Linux boxes) has offered advertisers ways to present short text messages along with targeted search results. These "sponsored links" have more in common with newspaper classifieds than with banners or any other form of graphical display advertising, and they have been the source of very few complaints. More importantly, they mostly seem to be working for everybody involved: users, advertisers and Google.
Recently, Google updated the program--previously called AdWords and now named AdWords Select--with a variety of improvements. For both users and advertisers, it improved the chances for relevant sponsored links.
But on Tuesday, February 19, the Associated Press put out a story by Michael Liedtke (here it is on the New York Times site) about the new program, delivering news that Google had morphed into yet another pay-for-placement search engine. It starts off this way:
Online search engine maker Google Inc. is introducing a program that allows Web sites to be displayed more prominently if sponsors pay more money--an advertising-driven system derided by critics as an invitation to deceptive business practices.
Four paragraphs pass before Liedtke writes:
Mountain View-based Google will continue to reserve most of its site for results sorted by relevance to a search request--a model that has cultivated a local following among Web surfers and turned the 300-employee company into one of the Internet's emerging power brokers.
But writing "continues to reserve most of its site" hardly deflects the thrust of the story, which is mostly about pay-for-placement.
Since AP is the primary source of news for countless newspapers and other news organizations, the story was picked up all over the place and then run under headlines that delivered the same bad news:
This whole situation proved to be one where the press release did a better job of telling the story.
As far as I've been able to tell, the only news organization that got the story right was CNET, where Lisa M. Bowman wrote "Google unveils new pay-for-play plan". But even there the headline gave the impression that Google was now a pay-for-placement search engine. And, as with the AP piece, the secondary story was about Google's "rivalry" with Overture Services, Inc., which seems the antithesis of Google: "The Leader in Pay-for-Performance" search services.
Of course, the whole thing got thrashed out on Slashdot, where a careful reader would gather that Google had, in fact, produced a system that improved matters for everyone concerned. Ads were still unobtrusive, and (among other improvements) advertisers paid only for actual click-throughs.
Here's how Cindy McCaffrey, Google's VP of Corporate Marketing, put it in an e-mail to me yesterday:
All we've done is modify our AdWords self-service program so that advertisers can pay on a CPC basis (this is good news). The search results continue to be as unbiased and objective as ever. We do not allow advertisers to influence rankings in any way through payment.
What remains to be seen is how much damage AP has done to Google's reputation.
Doc Searls is Senior Editor of Linux Journal.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide