Friday, August 12, 2011

[Gd] Fridaygram

| More

The official Google Code blog: Fridaygram


By Scott Knaster, Google Code Blog Editor

Back in June we launched GoogleCL, an open-source utility that provides command line access to Google services. For our friends who live on the command line and think mice are something cats chase, GoogleCL provides a handy way to perform various tasks, such as posting to Blogger or creating an appointment with Google Calendar. Sample commands look like this:
$ google blogger post --blog "Lemurland blog" --title "Latest Madagascar trip" --tags "vacation, ring-tailed" trip_post.html 

$ google calendar add "Order palm tree tomorrow at 10 AM"
GoogleCL works with various other Google services, providing access to YouTube, Picasa, Docs, and Contacts without having to deal with that pesky graphical user interface. And now, thanks to Google intern Michael Sittig and our APIs Discovery Service, GoogleCL supports all Discovery-based APIs – a list that includes Tasks, Moderator, Books, URL Shortener, and many others. For example, you can use the URL Shortener API to create a new short URL like so:
$ google urlshortener insert --longUrl www.example.com
As long as our fingers are firmly on the keyboard, let’s talk about words for a moment. The folks who make the Oxford Dictionaries have created Save the Words, a way to preserve wonderful but little-used English words. At Save the Words you can see these words, read their often-hilarious definitions, and agree to use them yourself to help obstrigillate this trend.

Finally, spend a moment taking a look at this article and then ask yourself: have explorers really found the Millennium Falcon at the bottom of the sea? (Spoiler alert: no.)

Even when they cover serious topics like Google APIs and purported spaceship wrecks, Fridaygram posts are just for fun. Each Fridaygram item must pass only one test: it has to be interesting to us nerds.
URL: http://googlecode.blogspot.com/2011/08/fridaygram.html

[Gd] Dev Channel Updates for Chromebooks

| More

Google Chrome Releases: Dev Channel Updates for Chromebooks

The Google Chrome team is happy to announce the release of Chrome 14.0.835.87 (Platform version: 811.34) on the Dev Channel for Chromebooks (Acer AC700, Samsung Series 5, and Cr-48).
Highlights:
  • Update the Netflix plugin to 1.1.3
  • Update Pepper Flash to version 10.3.200.105
Known issues:
  • 18953: Duplicate processes for apps / extensions shown in Task Manager


If you find new issues, please let us know by visiting our help site or filing a bug. You can also submit feedback using "Report an issue" under the wrench icon. Interested in switching to the Beta channel? Find out how.


Orit Mazor

Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/dev-channel-updates-for-chromebooks_11.html

[Gd] Dev Channel Update

| More

Google Chrome Releases: Dev Channel Update


The Dev channel has been updated to 15.0.849.0 for Windows, Linux, Chrome Frame and 15.0.849.1 for Mac.

All
  • Updated V8 3.5.2.0
  • [r96275] FTP: added directory listing parser for OS/2 format, Issue 92154
  • [r96073] FTP: fix directory listing parsing for Hylafax, Issue 90807
  • Large speed improvement for print preview
  • This release also contains fixes for many known stability issues.
Mac
  • [r95609] Replace the bookmark folder menus with native menus
  • [r96244] No overlay scrollbar in PDF on Lion, Issue 90530
Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta or Stable channels?  Find out how.  If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/dev-channel-update_11.html

[Gd] High-quality sites algorithm launched in additional languages

| More

Official Google Webmaster Central Blog: High-quality sites algorithm launched in additional languages

(Cross-posted on the Inside Search blog)



Webmaster level: All



For many months, we’ve been focused on trying to return high-quality sites to users. Earlier this year, we rolled out our “Panda” change for searches in English around the world. Today we’re continuing that effort by rolling out our algorithmic search improvements in different languages. Our scientific evaluation data show that this change improves our search quality across the board and the response to Panda from users has been very positive.



For most languages, this change impacts typically 6-9% of queries to a degree that a user might notice. This is distinctly lower than the initial launch of Panda, which affected almost 12% of English queries to a noticeable amount. We are launching this change for all languages except Chinese, Japanese, and Korean, where we continue to test improvements.



For sites that are affected by this algorithmic change, we have a post providing guidance on how Google searches for high-quality sites. We also have webmaster forums in many languages for publishers who wish to give additional feedback and get advice. We’ll continue working to do the right thing for our users and serve them the best results we can.



Posted by Amit Singhal, Google Fellow
URL: http://googlewebmastercentral.blogspot.com/2011/08/high-quality-sites-algorithm-launched.html

[Gd] Registration is now open for GDD Japan

| More

The official Google Code blog: Registration is now open for GDD Japan


By Phoebe Peronto, Developer Marketing Team

Registration continues to roll out for Google Developer Days! Following Monday’s announcement of GDD Argentina, Brazil, and Russia registration going live, GDD Japan registration is now open. You can access registration by visiting the newly launched GDD website Japan page and clicking on the “Register Now” link.

Registration for the other 4 GDD events is coming soon. Want more GDD? Visit the GDD 2011 website for event details, session updates, and, of course, registration.

Phoebe Peronto is a Developer Marketing Intern working to coordinate the launch of Google Developer Days 2011. She hails from UC Berkeley as a rising senior studying Political Science and Business, and is excited to work with the Google team for summer 2011.

Posted by Scott Knaster, Editor
URL: http://googlecode.blogspot.com/2011/08/registration-is-now-open-for-gdd-japan.html

[Gd] Google-hosted Custom Search Engines now use the Element

| More

Google Custom Search: Google-hosted Custom Search Engines now use the Element

Two months ago we announced that all Google-hosted Custom Search Engines would be upgraded to use the Element. We’re happy to report that that transition is now complete for all Custom Search users. Those that visit the Control Panel will find better tools for customizing the presentation of their CSEs.



Moving to the Element enables us to quickly deliver new features that Custom Search users can easily turn on for their sites and we will soon upgrade all iframe results to use embedded Elements.



As always, we look forward to your feedback.



Posted by: Liang Ch'ng, Software Engineer
URL: http://googlecustomsearch.blogspot.com/2011/08/google-hosted-custom-search-engines-now.html

Thursday, August 11, 2011

[Gd] Chrome Beta Channel Update

| More

Google Chrome Releases: Chrome Beta Channel Update

The Chrome Team is happy to announce the release of Chrome 14 to the Beta channel. 14.0.835.35 has been released for Windows, Mac, Linux and Chrome Frame. This update contains a number of new features and functionality, including:
  • Initial release of Native Client
  • Web Audio API
  • Additional Mac OS X Lion feature support
  • Sync Encryption for all data
  • Print Preview on Mac
  • Experimental Web Request extension API
  • Experimental Content Settings extension API
And a huge list of other fixes, changes, and stability improvements.  For more on Chrome 14, please visit the official Chrome blog. The full list of changes in this release are available in the SVN revision logs (trunk, branch). Interested in switching to the Beta channel? Find out how. If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/chrome-beta-channel-update.html

[Gd] Dev Channel Update

| More

Google Chrome Releases: Dev Channel Update


The Dev channel has been updated to 14.0.835.35 for Windows, Mac, Linux, and Chrome Frame.  This release contains an updated version of full screen mode for Mac OS X Lion, along with fixes for a number of stability issues on Lion and other platforms.  Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta or Stable channels?  Find out how.  If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/dev-channel-update_10.html

[Gd] Building Dynamic Applications with Data Pipelining, Templating and YQL

| More

OpenSocial API Blog: Building Dynamic Applications with Data Pipelining, Templating and YQL

Hello again everyone,



Today I wanted to go over one of the interesting things that you can do with OpenSocial using templating and data pipelining. Since these were introduced in version 0.9 of the specification, this functionality will not be available if:
  • The container that you are using does not support OpenSocial version 0.9 or later.
  • The container that you are using does not support data pipelining or templating.
With that said, let's get right down to an example. For this example, we're going to go through a few steps in order to scrape and display the recent headlines from Reddit:
  • We will use data pipelining to load in the headlines from Reddit.
  • The URL of the data pipe will be a dynamic call to the Yahoo! Query Language (YQL). YQL will be used to scrape the HTML from the page, then use an xpath to drill down to the repeating anchor tags that denote the headlines.
  • Lastly, from the JSON data that is returned back from YQL into the data pipe, we're going to use OpenSocial templating to display out the headline results.
Let's take a look at the gadget code behind this:

<?xml version="1.0" encoding="utf-8"?>

<Module>

<ModulePrefs title="Reddit Headline Fetch"

title_url="http://www.jcleblanc.com"

description="Obtains reddit.com headlines via YQL"

author="Jonathan LeBlanc">

<Require feature="opensocial-0.9"/>

<Require feature="opensocial-data" />

<Require feature="opensocial-templates" />

</ModulePrefs>

<Content type="html">

<![CDATA[

<script type="text/os-data" xmlns:os="http://ns.opensocial.org/2008/markup">

<os:HttpRequest key="reddit" href="http://query.yahooapis.com/v1/public/yql?

q=select%20*%20from%20html%20where%20url%3D%22http%3A%2F%2Fwww.reddit.com

%22%20and%0A%20%20%20%20%20%20xpath%3D'%2F%2Fa%5B%40class%3D%22title%22%5D'

&format=json"/>

</script>

<script type="text/os-template" require="reddit">

<ul>

<li repeat="${reddit.content.query.results.a}">

<a href="${Cur.href}">${Cur.content}</a>

</li>

</ul>

</script>

]]>

</Content>

</Module>
Let's break down the components of this gadget. First let's start with the meta data within the <ModulePrefs> node. There are three features that we will need to require:

   <Require feature="opensocial-0.9"/>

<Require feature="opensocial-data" />

<Require feature="opensocial-templates" />
First we have the OpenSocial version that we want to include. For our needs we can include version 0.9 of the specification since that will allow us to include the other features we need, namely our second and third Require statements for opensocial-data (Data Pipelining) and opensocial-templates (Templating). These three will give us the features that we need for the example.



Next we have the innards of the <Content> node. Let's explore the first <script> block:

   <script type="text/os-data" xmlns:os="http://ns.opensocial.org/2008/markup">

<os:HttpRequest key="reddit" href="http://query.yahooapis.com/v1/public/yql?

q=select%20*%20from%20html%20where%20url%3D%22http%3A%2F%2Fwww.reddit.com

%22%20and%0A%20%20%20%20%20%20xpath%3D'%2F%2Fa%5B%40class%3D%22title%22%5D'

&format=json"/>

</script>
This is our data pipelining section. When the gadget loads in the container that we are running it in, this section will issue an HTTP request to populate an object with the return value of the request. In our case this will be a GET request to the YQL service.



To define a data pipe, we set the type of the script block to text/os-data and then define the os XML namespace. Within the script block, we set the object that we want the data returned to to be "reddit". We then issue a data pipelining HTTP GET request to the YQL service, using the href attribute. This URL used includes the following components:
  • The public YQL URL: http://query.yahooapis.com/v1/public/yql
  • q: The YQL query to run, placed as a query string parameter.
  • format: The format to return our data in, in our case JSON. This is also placed as a query string parameter.
If we look at the query that we are using, we can see what the components of the request are:

  SELECT * FROM html WHERE url="http://www.reddit.com"

AND xpath='//a[@class="title"]'
YQL uses a query syntax much akin to SQL. In our request we are using the html table, which defines request functionality to allow us to scrape data from an HTML page and then apply an xpath to drill down to the nodes on the page that we want to capture. In our case, we are capturing all data from http://www.reddit.com where the xpath (or nodes that we want to return) is any anchor tag that contains a class of title. If we explore the source code of http://www.reddit.com we can see that each title on the page is indeed an anchor tag with a class of title. At the end of the request the reddit object should now contain the return value from the request or, in other words, the headlines from the Reddit homepage.



Now let's look at the templating script block:

<script type="text/os-template" require="reddit">

<ul>

<li repeat="${reddit.content.query.results.a}">

<a href="${Cur.href}">${Cur.content}</a>

</li>

</ul>

</script>
This is the block that will define the template for displaying our results. To define a templating script block, we define the type to be "text/os-template" and then we can include the object (in our case from the data pipelining request) that we want to make available to the template - we set this to "reddit" - the same value that we set as the key of the data pipelining request.



Now we can simply define the HTML that we want to use, with the variables, to display our results. For this simple use case we'll simply create an unordered list with all of the headlines displayed as anchor tag links. In OpenSocial templating, we can insert the value from a data source by including the variable that we want to act upon, displaying it in the format ${VARIABLE}. For instance, in our data pipe if we defined our key to be "foo" and in the foo object we have a sub-element named "bar", we could display it using ${foo.bar}. Another aspect about templating that we're going to be taking advantage of is repeaters. This will allow us to repeat a block of code for each object available, and is done so by adding a repeat="${OBJECT}" attribute on the block that should be repeated, in this case the <li> tag. This will create a list item for each headline we encounter.



Now, if we look at the HTML block knowing this, we can see that we are creating a root unordered list node, then creating a list item for each headline we encounter in the Reddit headlines object. The headlines are embedded in the object at reddit.content.query.results.a. Within each list item we display an anchor tag. The href of the anchor is set to that of the headline link and the text of the link is set to the headline that we get back from the query.



Once the gadget has rendered you should be presented with a very unstyled unordered list, which you may then apply CSS on to. Using this type of setup with a service like YQL, data pipelining, and templating, you can create gadgets that render very dynamic content while reducing the amount of coding that is needed.



Jonathan LeBlanc
Jonathan LeBlanc (@jcleblanc)

Jonathan LeBlanc is a principal developer evangelist with X.commerce. Jonathan has been a member of the OpenSocial community for over three years and is the author of O'Reilly's "Programming Social Applications".
URL: http://blog.opensocial.org/2011/07/building-dynamic-applications-with-data.html

[Gd] Beta and Stable Channel Update

| More

Google Chrome Releases: Beta and Stable Channel Update

The Chrome Beta and Stable channels have been updated to 13.0.782.112 which includes an updated version of Flash Player.  

The Chrome Team would especially like to thank Tavis Ormandy, the Google Security Team, and Google for donating a large amount of time and compute power to identify a significant number of vulnerabilities resolved in this release of Flash Player.  

We would also like to thank the Adobe team for their hard work on this security release.  You can find more detailed information about their release and the security bulletin.

Anthony Laforge
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/stable-channel-update_09.html

[Gd] New webmaster tutorial videos

| More

Official Google Webmaster Central Blog: New webmaster tutorial videos

Webmaster level: All



Over the past couple of years, we’ve released over 375 videos on our YouTube channel, with the majority of them answering direct questions from webmasters. Today, we’re starting to release a freshly baked batch of videos, and you might notice that some of these are a little different. Don’t worry, they still have Matt Cutts in a variety of colored shirts. Instead of only focusing on quick answers to specific questions, we’ve created some longer videos which cover important webmaster-related topics. For example, if you were wondering what the limits are for 301 redirects at Google, we now have a single video for that:







Thanks to everyone who submitted questions for this round. You can be the first to hear about the new videos as they’re released by subscribing to our channel or following us on Twitter.


Posted by Michael Wyszomierski, Search Quality Team
URL: http://googlewebmastercentral.blogspot.com/2011/08/new-webmaster-tutorial-videos.html

Tuesday, August 9, 2011

[Gd] A new, improved form for reporting webspam

| More

Official Google Webmaster Central Blog: A new, improved form for reporting webspam

Webmaster level: All


Everyone on the web knows how frustrating it is to perform a search and find websites gaming the search results. These websites can be considered webspam - sites that violate Google’s Webmaster Guidelines and try to trick Google into ranking them highly. Here at Google, we work hard to keep these sites out of your search results, but if you still see them, you can notify us by using our webspam report form. We’ve just rolled out a new, improved webspam report form, so it’s now easier than ever to help us maintain the quality of our search results. Let’s take a look at some of our new form’s features:


Option to report various search issues
There are many search results, such as sites with malware and phishing, that are not necessarily webspam but still degrade the search experience. We’ve noticed that our users sometimes report these other issues using our webspam report form, causing a delay between when a user reports the issue and when the appropriate team at Google handles it. The new form’s interstitial page allows you to report these other search issues directly to the correct teams so that they can address your concerns in a timely manner.


Simplified form with informative links
To improve the readability of the form, we’ve made the text more concise, and we’ve integrated helpful links into the form’s instructions. Now, the ability to look up our Webmaster Guidelines, get advice on writing actionable form comments, and block sites from your personalized search results is just one click away.


Thank you page with personalization options
Some of our most valuable information comes from our users, and we appreciate the webspam reports you submit to us. The thank you page explains what happens once we’ve received your webspam report. If you want to report more webspam, there’s a link back to the form page and instructions on how to report webspam more efficiently with the Chrome Webspam Report Extension. We also provide information on how you can immediately block the site you’ve reported from your personalized search results, for example, by managing blocked sites in your Google Account.


At Google, we strive to provide the highest quality, most relevant search results, so we take your webspam reports very seriously. We hope our new form makes the experience of reporting webspam as painless as possible (and if it doesn’t, feel free to let us know in the comments).


Posted by Jen Lee and Alissa Roberts, Search Quality Team
URL: http://googlewebmastercentral.blogspot.com/2011/08/new-improved-form-for-reporting-webspam.html

[Gd] Dev Channel Updates for Chromebooks

| More

Google Chrome Releases: Dev Channel Updates for Chromebooks

The Google Chrome team is happy to announce the release of Chrome 14.0.835.25 (Platform version: 811.26) on the Dev Channel for Chromebooks (Acer AC700, Samsung Series 5, and Cr-48).
Known issues:
  • False 3G connection error message (issue 18875)


If you find new issues, please let us know by visiting our help site or filing a bug. You can also submit feedback using "Report an issue" under the wrench icon. Interested in switching to the Beta channel? Find out how.


Orit Mazor

Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/dev-channel-updates-for-chromebooks.html

[Gd] Dev Channel Update

| More

Google Chrome Releases: Dev Channel Update


The Dev channel has been updated to 14.0.835.29 for Windows, Mac, Linux, and Chrome Frame. This release contains fixes for a number of issues, along with increased stability on Mac OS X Lion. Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta or Stable channels?  Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/08/dev-channel-update_08.html

Monday, August 8, 2011

[Gd] Registration is open for GDD Argentina, Brazil, & Russia

| More

The official Google Code blog: Registration is open for GDD Argentina, Brazil, & Russia


By Phoebe Peronto, Developer Marketing Team

As promised, registration for our first Google Developer Day events is open! You can register by visiting the newly launched GDD website and clicking on the “Register Now” link for the event you're interested in.
Registration for the other 5 GDD events is coming soon, so stay tuned.

Crave more GDD news? Visit the GDD 2011 website at http://www.google.com/events/developerday/2011 for event details, session updates, and, of course, registration.

Phoebe Peronto is a Developer Marketing Intern working to coordinate the launch of Google Developer Days 2011. She hails from UC Berkeley as a rising senior studying Political Science and Business, and is excited to work with the Google team for summer 2011.

Posted by Scott Knaster, Editor
URL: http://googlecode.blogspot.com/2011/08/registration-is-open-for-gdd-argentina.html