22 Aug 2019
The Official Google Blog
Next steps to ensure transparency, choice and control in digital advertising
Ads play a major role in sustaining the free and open web. They underwrite the great content and services that people enjoy and support a diverse universe of creators and publishers. But the ad-supported web is at risk if digital advertising practices don't evolve to reflect people's changing expectations around how data is collected and used.
The mission is clear: we need to ensure that people all around the world can continue to access ad supported content on the web while also feeling confident that their privacy is protected. As we shared in May, we believe the path to making this happen is also clear: increase transparency into how digital advertising works, offer users additional controls, and ensure that people's choices about the use of their data are respected.
Working together across the ecosystem
The web ecosystem is complex-it includes users, publishers, advertisers, technology and service providers, advocacy groups, regulatory bodies and more. We've seen that approaches that don't account for the whole ecosystem-or that aren't supported by the whole ecosystem-will not succeed. For example, efforts by individual browsers to block cookies used for ads personalization without suitable, broadly accepted alternatives have fallen down on two accounts.
First, blocking cookies materially reduces publisher revenue. Based on an analysis of a randomly selected fraction of traffic on each of the 500 largest Google Ad Manager publishers globally over the last three months, we evaluated how the presence of a cookie affected programmatic revenue. Traffic for which there was no cookie present yielded an average of 52 percent less revenue for the publisher than traffic for which there was a cookie present. Lower revenue for traffic without a cookie was consistent for publishers across verticals-and was especially notable for publishers in the news vertical. For the news publishers in the studied group, traffic for which there was no cookie present yielded an average of 62 percent less revenue than traffic for which there was a cookie present.1
Second, broad cookie restrictions have led some industry participants to use workarounds like fingerprinting, an opaque tracking technique that bypasses user choice and doesn't allow reasonable transparency or control. Adoption of such workarounds represents a step back for user privacy, not a step forward.
Exploring new privacy-forward standards for the web
Today, Chrome shared an update on their efforts to explore new foundational technologies for the web that will deliver on the vision laid out above-widespread access to free content and strong privacy for users. Chrome has offered a number of preliminary proposals to the web standards community in areas such as conversion measurement, fraud protection and audience selection. The goal of these proposals is to promote a dialog on ways browsers could advance user privacy, while still ensuring publishers can earn what they need to fund great content and user experiences, and advertisers can deliver relevant ads to the right people and measure their impact.
Getting the web standards community to work on developing a new set of technologies is a tall order, but it's not unprecedented. The community has worked together on a number of similar challenges over the years-such as gaining consensus to phase out browser plug-ins and reaching agreement to move away from Flash. We expect this will take years, not months, and we don't anticipate any near-term changes to how our ads products work on Chrome. But this is important work and we support the effort.
Pursuing a new level of ads transparency and user control
While Chrome explores new technologies for the web, we're also acting on the commitment we made in May of this year to increase the transparency of digital ads and offer users more control. Over the past few months, we've been listening to feedback from users and partners, and have arrived at an initial proposal to give people more visibility into and control of the data used for advertising. We've begun sharing this proposal for discussion to key industry and stakeholder groups and we're eager to hear and incorporate feedback.
Whether it's working with the standards community to explore a new set of technologies, or getting feedback from participants across the digital ads industry on a proposal to increase transparency and offer users more control, Google is committed to partnering with others to raise the bar for how data is collected and used. Only by working together can we define and implement new practices that result in better, more privacy-focused experiences for users while addressing the requirements of publishers and advertisers that fund and ensure access to free content on the web.
1. Google Ad Manager data; n=500 global publishers; Analysis based on an A/B experiment where cookies are disabled on a randomly selected fraction of each publisher's traffic; May-August 2019
22 Aug 2019 1:00pm GMT
Building a more private web
Privacy is paramount to us, in everything we do. So today, we are announcing a new initiative to develop a set of open standards to fundamentally enhance privacy on the web. We're calling this a Privacy Sandbox.
Technology that publishers and advertisers use to make advertising even more relevant to people is now being used far beyond its original design intent - to a point where some data practices don't match up to user expectations for privacy. Recently, some other browsers have attempted to address this problem, but without an agreed upon set of standards, attempts to improve user privacy are having unintended consequences.
First, large scale blocking of cookies undermine people's privacy by encouraging opaque techniques such as fingerprinting. With fingerprinting, developers have found ways to use tiny bits of information that vary between users, such as what device they have or what fonts they have installed to generate a unique identifier which can then be used to match a user across websites. Unlike cookies, users cannot clear their fingerprint, and therefore cannot control how their information is collected. We think this subverts user choice and is wrong.
Second, blocking cookies without another way to deliver relevant ads significantly reduces publishers' primary means of funding, which jeopardizes the future of the vibrant web. Many publishers have been able to continue to invest in freely accessible content because they can be confident that their advertising will fund their costs. If this funding is cut, we are concerned that we will see much less accessible content for everyone. Recent studies have shown that when advertising is made less relevant by removing cookies, funding for publishers falls by 52% on average1.
So we are doing something different. We want to find a solution that both really protects user privacy and also helps content remain freely accessible on the web. At I/O, we announced a plan to improve the classification of cookies, give clarity and visibility to cookie settings, as well as plans to more aggressively block fingerprinting. We are making progress on this, and today we are providing more details on our plans to restrict fingerprinting. Collectively we believe all these changes will improve transparency, choice, and control.
But, we can go further. Starting with today's announcements, we will work with the web community to develop new standards that advance privacy, while continuing to support free access to content. Over the last couple of weeks, we've started sharing our preliminary ideas for a Privacy Sandbox - a secure environment for personalization that also protects user privacy. Some ideas include new approaches to ensure that ads continue to be relevant for users, but user data shared with websites and advertisers would be minimized by anonymously aggregating user information, and keeping much more user information on-device only. Our goal is to create a set of standards that is more consistent with users' expectations of privacy.
We are following the web standards process and seeking industry feedback on our initial ideas for the Privacy Sandbox. While Chrome can take action quickly in some areas (for instance, restrictions on fingerprinting) developing web standards is a complex process, and we know from experience that ecosystem changes of this scope take time. They require significant thought, debate, and input from many stakeholders, and generally take multiple years.
To move things forward as quickly as possible, we have documented the specific problems we are trying to solve together, and we are sharing a series of explainers with the web community. We have also summarized these ideas today on the Chromium blog.
We look forward to getting feedback on this approach from the web platform community, including other browsers, publishers, and their advertising partners. Thank you in advance for your help and input on this process - we believe that we must solve these problems together to ensure that the incredible benefits of the open, accessible web continue into the next generation of the internet.
1 Google Ad Manager data; n=500 global publishers; Analysis based on an A/B experiment where cookies are disabled on a randomly selected fraction of each publisher's traffic; May-August 2019. More information available on the Google ads blog.
22 Aug 2019 1:00pm GMT
A pop of color and more: updates to Android’s brand
Over the last decade, Android's open platform has created a thriving community of manufacturers and developers that reach a global audience with their devices and apps. This has expanded beyond phones to tablets, cars, watches, TVs and more-with more than 2.5 billion active devices around the world. As we continue to build Android for everyone in the community, our brand should be as inclusive and accessible as possible-and we think we can do better in a few ways.
Android Q is Android 10
First, we're changing the way we name our releases. Our engineering team has always used internal code names for each version, based off of tasty treats, or desserts, in alphabetical order. This naming tradition has become a fun part of the release each year externally, too. But we've heard feedback over the years that the names weren't always understood by everyone in the global community.
For example, L and R are not distinguishable when spoken in some languages. So when some people heard us say Android Lollipop out loud, it wasn't intuitively clear that it referred to the version after KitKat. It's even harder for new Android users, who are unfamiliar with the naming convention, to understand if their phone is running the latest version. We also know that pies are not a dessert in some places, and that marshmallows, while delicious, are not a popular treat in many parts of the world.
As a global operating system, it's important that these names are clear and relatable for everyone in the world. So, this next release of Android will simply use the version number and be called Android 10. We think this change helps make release names simpler and more intuitive for our global community. And while there were many tempting "Q" desserts out there, we think that at version 10 and 2.5 billion active devices, it was time to make this change.
A refreshed look for the brand
The Android brand has evolved over time. Back in 2014, we updated our logo and brand color, and this year, we're introducing a more modern, accessible look.
The design of the logo draws inspiration from the most recognizable non-human member of the community, the Android robot. The robot belongs to everyone in the community, and has long been a symbol of the fun and curiosity at the heart of Android. Now, it has a special place in our logo.
We also changed the logo from green to black. It's a small change, but we found the green was hard to read, especially for people with visual impairments. The logo is often paired with colors that can make it hard to see-so we came up with a new set of color combinations that improve contrast.
We'll officially start using the updated logo in the coming weeks with the final release of Android 10. Thank you to the community for supporting Android and inspiring us over the years.
22 Aug 2019 1:00pm GMT
21 Aug 2019
Search Engine Land: News & Info About SEO, PPC, SEM, Search Engines & Search Marketing
Google rolls out maximize conversion value smart bidding strategy
It is now available in all Search campaigns.
Please visit Search Engine Land for the full article.
21 Aug 2019 3:49pm GMT
You can’t opt into or out of mobile-first indexing
Google's John Mueller reminds us that one day, there will only be mobile-first indexing.
Please visit Search Engine Land for the full article.
21 Aug 2019 2:21pm GMT
Are we right for fawning over core algorithm updates?
Every update Google rolls out needs to be discussed on some level but the amount of attention should be relative to its overall impact.
Please visit Search Engine Land for the full article.
21 Aug 2019 1:56pm GMT
04 Nov 2018
Matt Cutts: Gadgets, Google, and SEO
Halloween 2018: Crab claws!
Do you need something to cheer you up? You got it: I should explain this costume a little bit. At the US Digital Service, we do a thing called "crab claws." Crab claws is like visual applause-you pinch your fingers up and down to say "great job" or "congratulations" or "way to go." We do […]
04 Nov 2018 8:02pm GMT
08 Mar 2018
Matt Cutts: Gadgets, Google, and SEO
Some terrible personal news
Cindy Cutts, my wife and best friend, passed away earlier this week. While I was traveling for work recently, Cindy went to visit her family in Omaha, Nebraska. On Sunday, while enjoying time with family, Cindy started having trouble breathing. Her family quickly called 911 and paramedics took Cindy to the hospital, but Cindy lost […]
08 Mar 2018 12:17am GMT
22 Jan 2018
Matt Cutts: Gadgets, Google, and SEO
Talking to Mr. Money Mustache about the US Digital Service
Last week, I passed my one year anniversary as head of the US Digital Service (USDS). So when Mr. Money Mustache asked for an interview, I was delighted to talk about some of the work that the USDS does. If you aren't familiar with Mr. Money Mustache, he writes about a philosophy of badassity in […]
22 Jan 2018 6:58pm GMT
01 Apr 2017
Google Operating System
Google April Fools' Day 2017
April Fools' Day should probably be called Google Fools' Day, since there are so many Google hoaxes.
Google Japan developed a "bubble wrap" version of the Japanese keyboard. "The Google Japanese input bubble wrap version is a keyboard that realizes 'I want to press in my mind, I want to keep pressing'," according to Google Translate.
Another product for your smart home? Meet Google Gnome, "a voice-activated, hands-free tool designed to make backyard living effortless. Need to know what animal is squeaking in your bushes? Stay still and ask Gnome what sound an opossum makes. Running low on birdseed? That's where Gnome comes in. You can even use Gnome's proprietary high-intensity lasers to trim your hedges into whatever shape your heart desires."
The Chrome OS team brings the most popular mobile accessories to the Chromebook, which already blurs the line between mobile and desktop. Chromebook Groupie Stick, Chromebook Cardboard, Chromebook Workout Armband will soon be available in the Google Store. "To take advantage of beautiful, high-resolution displays, as well as great photo editing apps, we've carefully engineered the first Chromebook-sized selfie stick. Never again will you miss the perfect groupie."
Haptic Helpers make VR even more immersive. "We're taking VR to the next level with Haptic Helpers. Using a modest set of everyday tools, these VR virtuosos can simulate more than 10,000 unique experiences, all from the comfort of your own home. Smell the roses. Listen to the ocean. Feel a fluffy dog!"
You can now play the classic arcade game MS. PAC-MAN in Google Maps. "Avoid Blinky, Pinky, Inky, and Sue as you swerve the streets of real places around the world. But eat the pac-dots fast, because this game will only be around for a little while." Just go to the Google Maps site or open the Google Maps app for Android or iOS and click or tap MS. PAC-MAN at the bottom.
Google Cloud Platform expands to Mars. "By opening a dedicated extraterrestrial cloud region, we're bringing the power of Google's compute, network, and storage to the rest of the solar system, unlocking a plethora of possibilities for astronomy research, exploration of Martian natural resources and interplanetary life sciences. This region will also serve as an important node in an extensive network throughout the solar system. Our first interplanetary data center - affectionately nicknamed 'Ziggy Stardust' - will open in 2018," mentions Google.
Google Netherlands came up with Google Wind, a machine learning technology that controls the weather. "The Netherlands has many windmills, some no longer in use, we can connect to Google Cloud Platform. So we use the existing Dutch infrastructure, machine learning, weather patterns to control the network of windmills when rain is approaching. The first test results are very promising: we seem to be able to provide sun and clear skies for everyone in the Netherlands," mentions Google Netherlands blog.
Google's search app for iOS is now optimized for cats and dogs. "On the Google app for iOS, you can now use 3D Touch on the app icon or head to settings and select I'm Feeling Woof or I'm Feeling Meow to let your dogs and cats get info on topics they care about-whether that means squeaky toys or a bowl of milk!"
Google also launched Google Play for Pets, a new category of Android games designed for cats, dogs and other pets.
Google Translate's Word Lens feature supports a new language: Heptapod B, the alien language from the movie "Arrival". "The challenge with understanding Heptapod B is its nonlinear orthography. Fortunately, Google's neural machine translation system employs an encoder/decoder system that internally represents sentences as high-dimensional vectors. These vectors map well to the non-linear orthography of the Heptapod language and they are really the enabling technical factor in translating Heptapod B."
01 Apr 2017 7:25am GMT
19 Feb 2017
Google Operating System
Gmail Blocks JavaScript Attachments
If you try to send a JavaScript attachment using Gmail or if you want to download a .js attachment, you'll get a new anti-virus warning: "Blocked for security reasons", "1 attachment contains a virus or blocked file. Downloading this attachment is disabled".
.JS has been added to the long list of file types that are blocked by Gmail for security reasons. The full list: .ADE, .ADP, .BAT, .CHM, .CMD, .COM, .CPL, .EXE, .HTA, .INS, .ISP, .JAR, .JS (NEW), .JSE, .LIB, .LNK, .MDE, .MSC, .MSI, .MSP, .MST, .NSH .PIF, .SCR, .SCT, .SHB, .SYS, .VB, .VBE, .VBS, .VXD, .WSC, .WSF, .WSH. "To prevent against potential viruses, Gmail doesn't allow you to attach certain types of files, including: certain file types (listed above), including their compressed form (like .gz or .bz2 files) or when found within archives (like .zip or .tgz files), documents with malicious macros, archives whose listed file content is password protected, archives whose content includes a password protected archive."
The GSuite Blog informs that "for inbound mail, senders will get a bounce message explaining why the email was blocked. If you still need to send .js files for legitimate reasons, you can use Google Drive, Google Cloud Storage, or other storage solutions to share or send your files."
You can still send JavaScript files using Gmail if you change the extension. What about downloading old .js attachments? Try the workarounds from this post.
19 Feb 2017 10:39am GMT
25 Jan 2017
Google Operating System
Google Image Search Shows Colorful Suggestions
Google Image Search has a different way to display suggestions: it now shows a long list of colorful boxes with related searches. You can click one or more boxes to dynamically refine search results.
For example, when searching for [sportswear], Google shows suggestions like: [women basketball], [tennis], [badminton], [golf], [volleyball], [nike woman], [alexander wang], [adidas], [fashion], [performance], [vintage], [trendy], [urban], [school], [gym], [90's], [70's], [vogue], [luxe], [avant garde], [korean], [italian], [french] and more. It's interesting to notice that each category of suggestions has a different color.
Here's the old interface, which had fewer suggestions and displayed thumbnails next to suggestions:
25 Jan 2017 9:39pm GMT
11 Nov 2011
Search Engine Watch - Latest
Google’s Timeline Search Option is History
As Google pushes fresh search results, a helpful Google search tool for historical searches quietly vanished earlier this month. Google has confirmed that Google's Timeline search option, which debuted in 2007, has been discontinued. By cl...
11 Nov 2011 9:35pm GMT
Google Releases Think Insights Trend & Research Hub for Marketers
Google has graduated Think Insights from beta. This tool now compiles real-time data from Google search and other platforms, combining those facts with additional studies, infographics, and more. Users can find the site at ThinkwithGoogle.com, a...
11 Nov 2011 8:45pm GMT
Google Snaps Up Katango, Social Contact Sorter Meant for Facebook
Google has just acquired startup Katango, makers of a Facebook friends list generating iPhone app released this July. Shortly after its debut, however, Katango's autogenerator faced serious competition from Facebook itself, as it rolled out ...
11 Nov 2011 7:35pm GMT
06 Nov 2011
Planet Arch Linux
Tyrs a Microblogging Client based on Ncurses
Tyrs is a microblogging client, supporting Twitter and Status.net (identi.ca), it's based on console using the NCurses module from Python. The release of the 0.5.0 version is a good excuse to introduce Tyrs. Tyrs aims to get a good interaction with a fairly intuitive interface that can provide support ncurses. Tyrs tries also not to [...]
06 Nov 2011 9:43pm GMT
About.com Architecture
Born on November 6: Jean Louis Charles Garnier
French architect Jean Louis Charles Garnier was born on November 6, 1825. Inspired by Roman pageantry, Garnier wanted ...
06 Nov 2011 1:00am GMT
05 Nov 2011
Planet Arch Linux
Pulling strings
After one year of managing a network of 10 servers with Cfengine I'm currently building two clusters of 50 servers with Puppet (which I'm using for the first time), and have various notes to share. With my experience I had a feeling Cfengine just isn't right for this project, and didn't consider it seriously. These servers are all running Debian GNU/Linux and Puppet felt natural because of the good Debian integration, and the number of users whom also produced a lot of resources. Chef was out of the picture soon because of the scary architecture; CouchDB, Solr and RabbitMQ... coming from Cfengine this seemed like a bad joke. You probably need to hire a Ruby developer when it breaks. Puppet is somewhat better in this regard.
Puppet master needs Ruby, and has a built-in file server using WEBrick. My first disappointment with Puppet was WEBrick. Though PuppetLabs claim you can scale it up to 20 servers, that proved way off, the built-in server has problems serving as little as 5 agents/servers, and you get to see many dropped connections and failed catalog transfers. I was forced to switch to Mongrel and Nginx as frontend very early in the project, on both clusters. This method works much better (even though Apache+Passenger is the recommended method now from PuppetLabs), and it's not a huge complication compared to WEBrick (and Cfengine which doesn't make you jump through any hoops). Part of the reason for this failure is my pull interval, which is 5 minutes with a random sleep time of up to 3 minutes to avoid harmonics (which is still a high occurrence with these intervals and WEBrick fails miserably). In production a customer can not wait on 30/45 minute pull intervals to get his IP address whitelisted for a service, or some other mundane task, it must happen within 10 minutes... but I'll come to these kind of unrealistic ideas a little later.
Unlike the Cfengine article I have no bootstrapping notes, and no code/modules to share. By default the fresh started puppet agent will look for a host called "puppet" and pull in what ever you defined to bootstrap servers in your manifests. As for modules, I wrote a ton of code and though I'd like to share it, my employer owns it. But unlike Cfengine v3 there's a lot of resources out there for Puppet which can teach you everything you need to know, so I don't feel obligated to even ask.
Interesting enough, published modules would not help you get your job done. You will have to write your own, and your team members will have to learn how to use your modules, which also means writing a lot of documentation. Maybe my biggest disappointment is getting disillusioned by most Puppet advocates and DevOps prophets. I found articles and modules most of them write, and experiences they share have nothing to do with the real world. It's like they host servers in a magical land where everything is done in one way and all servers are identical. Hosting big websites and their apps is a much, much different affair.
Every customer does things differently, and I had to write custom modules for each of them. Just between these two clusters a module managing Apache is different, and you can abstract your code a lot but you reach a point where you simply can't push it any more. Or if you can, you create a mess that is unusable by your team members, and I'm trying to make their jobs better not make them miserable. One customer uses an Isilon NAS, the other has a content distribution network, one uses Nginx as a frontend, other has chrooted web servers, one writes logs to a NFS, other to a Syslog cluster... Now imagine this on a scale with 2,000 customers and 3 times the servers and most of the published infrastructure design guidelines become laughable. Instead you find your self implementing custom solutions, and inventing your own rules, best that you can...
I'm ultimately here to tell you that the projects are in a better state then they would be with the usual cluster management policy. My best moment was an e-mail from a team member saying "I read the code, I now understand it [Puppet]. This is fucking awesome!". I knew at that moment I managed to build something good (or good enough), despite the shortcomings I found, and with nothing more than using PuppetLabs resources. Actually, that is not completely honest. Because I did buy and read the book Pro Puppet which contains an excellent chapter on using Git for collaboration on modules between sysadmins and developers, with proper implementation of development, testing and production (Puppet)environments.
05 Nov 2011 11:17pm GMT
Dexigner
Adobe Muse Beta 4 with 40+ New Enhancements
Adobe released an update to its Muse software with Muse Beta 4. This update delivers more than 40 new enhancements, and is now available in five additional languages: French, German, Spanish, Swedish and Dutch.
"With more than 330,000 beta downloads to date, Muse continues to empower designers globally," said Lea Hickman, vice president of Design and Web product management at Adobe. 
05 Nov 2011 4:56am GMT
The Register of Chartered Designers
The Chartered Society of Designers announced that The Queen has approved an Order amending the Royal Charter of the Society granting it the power to award the designation of Chartered Designer and to Maintain a Register of those Chartered Designers.
The original charter granted in 1976 recognised the efforts of the Society since its inception in promoting and fostering professional study and practice. It also set out objects which included achieving a recognised profession of design. 
05 Nov 2011 4:20am GMT
Camo Bear: Perfect Fools Creates New Online Film for Nikon
Perfect Fools launched "Camo Bear," a fun viral film, as part of an online campaign for Nikon Coolpix AW100. The film is a 90-second short designed to demonstrate how hardwearing the Nikon Coolpix AW100 is.
The hero of the film is Camo Bear, a camouflage-coloured, extreme sports enthusiast who lives life to the max. 
05 Nov 2011 4:06am GMT
Planet Arch Linux
Jshon
Creating json is now ten times easier.
05 Nov 2011 3:10am GMT
04 Nov 2011
About.com Architecture
Architecture Updates: Oct. 29-Nov. 4, 2011
Postmodernism, house plans, and New Orleans captured our attention this week. Updated material includes:
- New Orleans Now
- Before You Buy House Plans
- Robert Venturi, Postmodern Architect
- Denise Scott Brown, Venturi, Scott Brown & Associates
- The Vanna Venturi House
- ...
04 Nov 2011 10:30am GMT
The Dawn of Deco
Archaeologist Howard Carter thrilled the world when, on November 4, 1922, he discovered steps leading down to the ancient tomb of King Tutankhamen. Soon a fascination for Egypt found expression ...
04 Nov 2011 1:00am GMT
26 Aug 2011
Google Blogoscoped
The Emperor's Garden
The Emperor instructed the gardener to set up the new court's garden. "I want you to plant five trees growing the Crataan fruit," the Emperor said, "Because we asked people what fruit they like best, and most named the Crataan fruit!" The gardener replied, "Emperor, that is excellent thinking! But let me make some suggestions: First, how about we make one of the five trees bear the Muran fruit. Only one out of ten citizens loves it, but those peculiar citizens tend to love multiple times as much!" "Second," the gardener continued, "How about we make one of the five trees bear the Dratean fruit. No one loves it, but that's because no one knows it yet!" "Third," the gardener said, "How about we leave one spot in the garden empty. Who knows what new type of tree we'll discover that we can put there in the fut ...
26 Aug 2011 12:12pm GMT
15 Aug 2011
Google Blogoscoped
Color Sound Machine (and what else I've been doing lately)
For those of you who've been wondering whether I had turned to stone, fallen into a bottomless pit, or been climbing the Himalaya... no, none of that is true, even though you probably did notice I'm not actively blogging about Google here anymore*! Just now, a new iPad app I've been working on called Color Sound Machine went live, and this -- and all the other apps and games at Versus Pad** -- are actually what I am doing while not blogoscoping. *I've drafted unpublished posts explaining much more about past, present and future of Blogoscoped, and the history of Google news reporting, but ... oh, for now le ...
15 Aug 2011 4:00pm GMT
25 Feb 2011
Google Blogoscoped
Google drops reverse phone number lookup
One of the earliest specialist services provided by Google was reverse phone number lookup. If you used the "phonebook:" or "rphonebook:" operators together with a 10-digit US phone number, Google would show you the owner of that phone number, unless the number was unlisted. Google no longer provides that service. Not surprisingly, there was no press release marking the closure, but Google employee Daniel Russell has acknowledged the closure of the service in his blog. He hints at the possible pressures leading to the shuttering of the service: "As you can imagine, this was an endless source of hassles for people (who were surprised to see themselves searchable on Google) and for Google (who had to constantly de ...
25 Feb 2011 11:23am GMT