OpenSocial continues to grow: Welcome, Yahoo!

Filed under: Official Google Blog — Wrote by Lees on Sunday, May 4th, 2008 @ 2:27 am

Posted by Dan Peterson, Product
Manager

Last November, href="http://googleblog.blogspot.com/2007/11/opensocial-makes-web-better.html"
id="acjj" >OpenSocial was created to help build infrastructure
for the social web. OpenSocial provides a common mechanism for
developers to easily hook into many different social networks and
extend their functionality. Sites including MySpace and orkut have
begun to provide OpenSocial applications to their users, and hi5
will be rolling out next week.

Today we're pleased that href="http://ycorpblog.com/2008/03/25/announcing-the-opensocial-foundation/" >
Yahoo! has announced its support for OpenSocial. We're
looking forward to having Yahoo! users join the hundreds of
millions of people who will soon enjoy OpenSocial applications.
This addition means even more distribution for developers,
encourages participation by even more websites, and, most
importantly, results in more features for users all across the
web.

In addition, Yahoo!, MySpace, and Google are joining with the
broader community to create a non-profit foundation to foster the
continued open development of OpenSocial. To that end, we've
also launched href="http://www.opensocial.org/" >OpenSocial.org, designed to
become the main documentation hub and primary source of information
about OpenSocial. To learn more, and to get involved, please review
the href="http://sites.google.com/a/opensocial.org/opensocial/OpenSocial-Foundation-Proposal" >
foundation proposal.

With that, welcome, Yahoo! We look forward to growing the social
web together.

Tags: , , , , , , ,

Team Aquaduct wins Innovate or Die competition

Filed under: Official Google Blog — Wrote by Lees on Tuesday, April 15th, 2008 @ 3:50 am

Posted by Dan Reicher, Google.org
team

The contest said to "Innovate or Die" – and Team Aquaduct
lives! In fact, the San Bruno, California team – consisting of John
Lai, Adam Mack, Brian Mason, Eleanor Morgan, Paul Silberschatz – is
living in grand (prize) style today after winning the href="http://googleblog.blogspot.com/2007/09/pour-on-pedal-power.html" >
first Innovate or Die Pedal-Powered Machine contest.

Team Aquaduct was declared the winner out of 102 entries by
building a unique and functional solution to provide rural
communities with access to clean water. The quintet will share the
$5,000 grand prize, and each will receive a Specialized Globe
bicycle – as will all five of the finalist runners-up ( href="http://www.innovate-or-die.com/" >read more about all the
winners).

The contest encouraged people to evaluate environmental issues and
develop ingenious solutions surrounding climate change. Many
original and inspiring ideas emerged; make sure to visit the href="http://www.youtube.com/groups_videos?name=innovateordie" >YouTube
Innovate or Die page to view all of the entries.

And here's the video for Team Aquaduct's winning
pedal-powered water transportation and filtration vehicle:

value="http://www.youtube.com/v/-U-mvfjyiao&rel=1" /> type="application/x-shockwave-flash" wmode="transparent"
height="355" width="425" />

Tags: , , , , , , ,

A clean energy update

Filed under: Official Google Blog — Wrote by Lees on Tuesday, December 11th, 2007 @ 6:18 am

Posted by Dan Reicher, Director,
Climate and Energy Initiatives, Google.org

Today Google.org is launching an
exciting project that offers a glimpse of a smarter energy future:
cars that plug into an electric grid powered by solar energy.
Plug-in hybrid electric vehicles (“plug-in hybrids”) can achieve 70
-100 miles per gallon, quadrupling the fuel economy of the average
car on the road today (~20 mpg). As we demonstrated at today’s
event, plug-in hybrids can sell power back to the electric grid
when it's needed most through vehicle-to-grid (V2G)
technology

As you may know, one of Google.org's core missions is to
address climate change. In the U.S., transportation contributes
about one-third of all greenhouse gas emissions –- with more than
60 percent of those emissions coming from personal vehicles. By
accelerating the adoption of plug-in hybrids and vehicle-to-grid
("V2G") technologies, this new project, href="http://www.google.org/recharge/" >RechargeIT.org, aims to
reduce emissions and dependence on oil while promoting clean energy
technologies and increasing consumer choice. Linking the U.S.
transportation system to the electricity grid maximizes the
efficiency of our energy system. From these efforts, we believe the
environment will benefit — and consumers will have more choices to
fuel their cars.

We've been working with Google engineers and href="http://www.hymotion.com/" >Hymotion/ href="http://www.a123systems.com/" >A123Systems to build a small
fleet of plug-in hybrids, adding an external plug and additional
batteries to a regular hybrid car so that it runs on electricity
with gasoline (or even better, biofuels) to extend the driving
range for longer trips. Here's what it looks like:

onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"
href="http://bp1.blogger.com/_Ap14FtNN91w/RnbA4qOTHOI/AAAAAAAAAJc/fYo3rIHjp_0/s1600-h/PHEV_car.png" >
alt="" id="BLOGGER_PHOTO_ID_5077457709546282210"
border="0" />

Since most Americans drive less than 35 miles per day, you easily
could drive mostly on electricity with the gas tank as a
"safety net." Our goal is to demonstrate the plug-in
hybrid and V2G technology, get people excited about having their
own plug-in hybrid, and encourage car companies to start building
them soon.

In the preliminary results from our test fleet, on average the
plug-in hybrid gas mileage was 30 mpg higher than that of the
regular hybrids. In conjunction with Pacific Gas and Electric, we
also demonstrated the bidirectional flow of electricity through V2G
technology, and have awarded $1 million in grants and announced
plans for a $10 million request for proposals (RFP) to fund
development, adoption and commercialization of plug-ins, fully
electric cars and related vehicle-to-grid (V2G) technology.
(Here's the href="http://www.google.com/intl/en/press/pressrel/rechargeit_20070618.html" >
full release.)

As for Google Inc., today the href="http://googleblog.blogspot.com/2006/10/corporate-solar-is-coming.html" >
solar panel installation we announced last October is now
producing clean, renewable electricity for our Mountain View, CA
headquarters.

onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"
href="http://bp0.blogger.com/_Ap14FtNN91w/RnbFfaOTHQI/AAAAAAAAAJs/8czOFPmqUGg/s1600-h/Solarpanels_patio.png" >
alt="" id="BLOGGER_PHOTO_ID_5077462773312724226"
border="0" />

The system will offset peak electricity consumption at the solar
powered offices and the newly constructed solar carports have
charging stations for the plug-in hybrids. At 1.6 megawatts — with
an electricity output capable of powering approximately 1,000
average California homes — the Google project is the largest solar
installation on any corporate campus in the U.S. to date, and one
of the largest on any corporate site in the world. To see how much
electricity these panels are producing right now, visit our new href="http://www.google.com/corporate/solarpanels" >performance
monitoring site.

To learn more about the initiative, we encourage you to explore the
rest of href="http://www.google.org/recharge/" >RechargeIT.org. And to
see what others are saying about plug-in hybrids and V2G
technology, be sure to watch this video.

value="http://www.youtube.com/v/oDjSbWTJbdo" /> type="application/x-shockwave-flash" wmode="transparent"
height="350" width="425" />

Tags: , , , , , , ,

Computer science resources for academics

Filed under: Official Google Blog — Wrote by Lees on Saturday, December 8th, 2007 @ 8:50 pm

Posted by Dan Peterson, Product
Manager

Google has a long history of involvement with universities, and
we're excited to share some recent news on that front with you.
At the main Google campus this week we're hosting the href="http://www.google.com/events/facultysummit2007/agenda.html" >Google
Faculty Summit, which involves href="http://www.stanford.edu/" >universities href="http://www.uiuc.edu/" >all href="http://www.mit.edu/" >over participating in discussions
about what we're up to in research-land as well as computer
science education - something very near and dear to us.

Meanwhile, because we know that between teaching, doing research
and advising students, computer science educators are quite
strapped for time, we've recently launched a site called href="http://code.google.com/edu/" >Google Code for Educators.
While you may have previously heard about our href="http://www.google.com/educators/index.html" >offerings for
K-12 teachers, this new program is focused on CS topics at the
university level, and lets us share the knowledge we've built
up around things like distributed systems and AJAX programming.
It's designed for university faculty to learn about new
computer science topics and include them in their courses, as well
as to help curious students learn on their own.

Right now, Google Code for Educators offers materials for AJAX web
programming, distributed systems and parallel programming, and web
security. The site includes slides, programming labs, problem sets,
background tutorials and videos. We're eager to provide more
content areas and also more iterations for existing topic areas. To
allow for liberal reuse and remixing, most sample course content on
Code EDU is available under a href="http://creativecommons.org/" >Creative Commons license.
Please let us know href="http://groups.google.com/group/Google-Code-for-Educators" >your
thoughts on this new site.

Beyond CS education, another important faculty topic is research.
Google Research offers
resources to CS researchers,including papers authored by Googlers
and a wide variety of our tech talks. You might be interested in
learning more about href="http://labs.google.com/papers/mapreduce.html" >MapReduce
and the Google
File System
, two pieces of Google-grown technology that have
allowed us to operate at enormous scale. We also recently put
together a few university research programs and we're eager to
see what academics come up with. height="1" width="1" />

Tags: , , , , , , ,

Robots Exclusion Protocol: now with even more flexibility

Filed under: Official Google Blog — Wrote by Lees on Saturday, December 8th, 2007 @ 8:50 pm

Posted by Dan Crow, Product
Manager

This is the third and last in my series of blog posts about the
Robots Exclusion Protocol (REP). In the href="http://googleblog.blogspot.com/2007/01/controlling-how-search-engines-access.html" >
first post, I introduced robots.txt and the robots
META tags, giving an
overview of when to use them. In the href="http://googleblog.blogspot.com/2007/02/robots-exclusion-protocol.html" >
second post, I shared some examples of what you can do with the
REP. Today, I'll introduce two new features that we have
recently added to the protocol.

As a product manager, I'm always talking to content providers
to learn about your needs for REP. We are constantly looking for
ways to improve the control you have over how your content is
indexed. These new features will give you flexible and convenient
ways to improve the detailed control you have with Google.

Tell us if a page is going to
expire
Sometimes you know in advance that a page is going to expire in the
future. Maybe you have a temporary page that will be removed at the
end of the month. Perhaps some pages are available free for a week,
but after that you put them into an archive that users pay to
access. In these cases, you want the page to show in Google search
results until it expires, then have it removed: you don't want
users getting frustrated when they find a page in the results but
can't access it on your site.

We have introduced a new META tag that allows you to
tell us when a page should be removed from the main Google web
search results: the aptly named unavailable_after tag. This
one follows a similar syntax to other REP META tags. For example, to
specify that an HTML page should be removed from the search results
after 3pm Eastern Standard Time on 25th August 2007, simply add the
following tag to the first section of the page:

<META
NAME="GOOGLEBOT" CONTENT="unavailable_after:
25-Aug-2007 15:00:00 EST">

The date and time is specified in the href="http://www.ietf.org/rfc/rfc0850.txt" >RFC 850
format.

This information is treated as a removal request: it will take
about a day after the removal date passes for the page to disappear
from the search results. We currently only support unavailable_after for
Google web search results.

After the removal, the page stops showing in Google search results
but it is not removed from our system. If you need a page to be
excised from our systems completely, including any internal copies
we might have, you should use the existing URL removal tool which
you can read about on our href="http://googlewebmastercentral.blogspot.com/2007/04/requesting-removal-of-content-from-our.html" >
Webmaster Central blog.

Meta tags everywhere
The REP META tags
give you useful control over how each webpage on your site is
indexed. But it only works for HTML pages. How can you control
access to other types of documents, such as Adobe PDF files, video
and audio files and other types? Well, now the same flexibility for
specifying per-URL tags is available for all other files
type.

We've extended our support for META tags so they can now
be associated with any file. Simply add any supported META tag to a new X-Robots-Tag directive in
the href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html" >HTTP
Header used to serve the file. Here are some illustrative
examples:

Don't display a cache link or snippet for this item in the
Google search results:

X-Robots-Tag: noarchive,
nosnippet

Don't include this document in the Google search
results:

X-Robots-Tag:
noindex

Tell us that a document will be unavailable after 7th July
2007, 4:30pm GMT:

X-Robots-Tag:
unavailable_after: 7 Jul 2007 16:30:00 GMT

You can combine multiple directives in the same document. For
example:

Do not show a cached link for this document, and remove it from
the index after 23rd July 2007, 3pm PST:

X-Robots-Tag:
noarchive
X-Robots-Tag: unavailable_after: 23 Jul 2007 15:00:00
PST

Our goal for these features is to provide more flexibility for
indexing and inclusion in Google's search results. We hope you
enjoy using them. height="1" width="1" />

Tags: , , , , , , ,

Google Web Toolkit: Towards a better web

Filed under: Official Google Blog — Wrote by Lees on Friday, December 7th, 2007 @ 10:36 pm

Posted by Bruce Johnson and Dan
Peterson, Google Web Toolkit team

We're very pleased to tell you that the href="http://code.google.com/webtoolkit/" >Google Web Toolkit
(GWT) is no longer in beta as of href="http://googlewebtoolkit.blogspot.com/2007/08/gwt-14-release-and-out-of-beta.html" >
today's release of GWT 1.4. For Java developers who have
used GWT to create high-end web applications over the last year,
this may not seem all that surprising. But if you haven't yet
heard the story behind GWT, this seems like the perfect
time…

If you've been in the technology industry for a while, you
probably remember when enterprises and software vendors had to
think pretty hard about whether to develop locally-installed
desktop applications or web-based browser applications. These days,
whether you're building href="http://code.google.com/gme/" >mashups, href="http://code.google.com/apis/gadgets/" >gadgets, or
full-blown applications, it's a no-brainer: the browser is the
delivery platform of choice. However, users expect more from the
up-and-coming generation of web applications than the simple
click-and-wait of yesterweb. And if you're a web developer, you
know that this requires href="http://en.wikipedia.org/wiki/Ajax_(programming)" >AJAX,
the cluster of technologies including JavaScript and dynamic HTML
that can make browsers do backflips.

But the stark reality of AJAX applications is that, although they
can deliver sexy features and great usability, they are unusually
hard to engineer. Browser quirks and the anything-goes nature of
JavaScript will inevitably frustrate even the most dedicated
developers and add risk to your schedule with every line of code
written. If you do eventually manage to construct a complex AJAX
application that works, you're likely to find that maintaining
it over time can be a major challenge. And all that doesn't
even scratch the surface of testing, optimizing, securing and
internationalizing your application. (If you are currently working
on an ambitious AJAX project and haven't yet come to this
conclusion, please re-read this post in six months when you're
further along!)

We've learned a lot from our experiences building web
applications, and we're happy to share the tools we've
created. Google Web Toolkit is an open source project that helps
Java developers harness the richness of AJAX in a cross-platform,
web-friendly environment. The magic trick is that GWT
cross-compiles Java source code into standalone JavaScript that you
can include in any web page. Instead of spending time becoming
JavaScript gurus and fighting browser quirks, developers using GWT
spend time productively coding and debugging in the robust Java
programming language, using their existing Java tools and
expertise. Naturally, GWT is also a great way to easily take
advantage of the latest-and-greatest Google APIs and browser
enhancements, such as href="http://code.google.com/apis/gears/" >Google Gears.

In addition to making debugging far easier, GWT's unique
compilation-based approach to AJAX has the nice property that it
rewards developers for good software engineering practices. Java
source code that is clear and organized can be easily optimized by
the GWT compiler, which is a nice antidote to the frequent
hack-and-slash approach that's all too common in JavaScript
development. As your application grows, the GWT compiler begins to
pay off in even bigger ways. Unused code is automatically removed
so that scripts are smaller and pages load faster. Complex code can
be automatically coalesced and simplified. Most importantly,
because the Java language is statically typed, many common errors
can be caught during development rather than production. You can
observe the high-performance results yourself in GWT's href="http://gwt.google.com/samples/Mail/Mail.html" >sample Mail
application.

Technical details aside, GWT makes it easy to develop fast,
friendly web apps that users love — which is, after all, the
point.

Download
GWT 1.4
. height="1" width="1" />

Tags: , , , , , , ,

Pour on the pedal power

Filed under: Official Google Blog — Wrote by Lees on Friday, December 7th, 2007 @ 2:15 am

Posted by Dan Reicher, Google.org

You may already know that we're working to reduce our impact on
the environment in a number of ways. We opt for locally-grown food
whenever possible in all of our cafes. We've covered our roofs
with solar panels. We offer a rebate on our employees'
fuel-efficient car purchases. When it comes to getting people to
the office, we offer round-trip shuttle service to our Bay Area
Googlers, as well as incentives for creative commuting, from
walking to biking and even to kayaking (depending, of course, on
where the office is).

Over at Google.org, the href="http://www.google.org/recharge/" >RechargeIT project is href="http://www.google.org/recharge/dashboard" >collecting data
on plug-in hybrid electric vehicles (PHEVs) in an effort to
accelerate commercial adoption of the cars as well as vehicle to
grid technology. To the same end, we just issued a $10 million
request for investment proposals to encourage companies and
individuals to develop sustainable transportation solutions.

And now, we encourage all of you to get your wheels spinning to
offset climate change. Google has teamed up with href="http://www.specializedbikes.com/" >Specialized and href="http://www.goodbysilverstein.com/main_site/main.html" >Goodby
Silverstein & Partners on the href="http://www.innovate-or-die.com/" >Innovate or Die
Pedal-Powered Machine Challenge, to give you problem-solvers a
chance to show us with a YouTube href="http://www.youtube.com/group/innovateordie" >video how you
harness pedal power in innovative ways. In January, you could win
$5,000 in cash and Specialized Globe bikes to keep up your
commitment. We're doing our bit to support new solutions. Are
you feeling inspired? height="1" width="1" />

Tags: , , , , , , ,

Control search engine is visited and index your website

Filed under: Google Blackboard — Wrote by Lees on Wednesday, November 21st, 2007 @ 9:11 am

The person that publish Dan Crow, product manager
Reprint fromWebsite of cereal song Chinese governs a rich settle or live in a strange place

Textual:
Controlling How Search Engines Access And Index Your website

Publish at: On January 26, 2007 morning 11:36:00

I often am asked about Google (Gu Ge) all alone with search how engine runs. Problem of a core is: How is Gu Ge to know the what part of a website is a website possessory want to let them show in searching a result? Can website content promulgator appoint partial website to be not searched? Good news is, the webpage that website content promulgator can use a lot of methods to control you is searching a result to show mediumly.

File Robots.txt is the leading role here, this file has made industry standard a lot of years. It makes a website possessory control search engine to visit their website. You can use ground of Robots.txt disparate arrangement of ideas to dominate a visit, let search engine to visit whole website only for instance, individual catalog, the webpage of specific type, or some webpage. Use Robots.txt effectively to be able to let you control the search of the website to you better, but how achieving this one goal is not very of clearly. This is the first of a series of cards of the access that we control the website to you about how using Robots.txt.

What does file Robots.txt have to use?

Internet is very big really. You just do not believe it is how the ground is endless the ground is big. You perhaps think to safeguard a website to expend a lot of energy, but that is only ” net Hai Yisu ” . (pay cordial apology to Douglas Adams)

Such search engine can read song elephantine cereal to take all news and index to these information, index is to let engine of a search show the webpage that matchs to it to inquiry of a few users.

To accomplish a few computer of this cereal song ceaseless capture website, they have the list of all websites that a Gu Ge knows, they read all webpages of every website. All these machines are called ballad Googlebot. Generally speaking, you are the website that is willing to let Googlebot visit you, such your webpages just can be gone to in Gu Ge search by people.

However, to some a few pages on your website, you may not want to let Gu Ge index. E.g. , you may have a catalog to include in-house daily record, or you may have some of news article to be able to be in only visit of the ability after paying fee. You can pass the file that founds name of file of a text to be Robots.txt to place it in root catalog to come down to tell Gu Ge reptile does not go capture they. File Robots.txt included the detailed account of the page that engine of a search cannot visit. Founding a Robots.txt is blunt, it promises you to use a nicety statified the visit of control search engine to your website.

Careful control

The one pile document that allows you to be you besides Robots.txt file is concise and clear give out outside the instruction, you also can use Robots META label to dominate the visit of individual to yours webpage accurately. To accomplish this, you need to add specific META label to be controlled how to index to individual webpage to your HTML webpage only. Return and anyhow, robots.txt and META label make you more agile and upper amount to complex visit provision to become quite easily.

A simple case

Here is a simple case, it is file of a Robots.txt.

User-Agent: Googlebot
Disallow: / Logs/

An instruction of facial cent below demonstrate of User -Agent travel just is Googlebot. Engine of all and main search is read and be subject to the statement that you put in Robots.txt. Want you to be willing only, you can think different search engine appoints different regulation. Disallow tells Googlebot to cannot enter the subdirectory of record daily record of your website all right. The content that you put in log catalog will not show in cereal the song searchs a result in.

Prohibit visitting individual file

If you have to register the article that user ability visits only, you want to let it eliminate to be besides Gu Ge’s result certainly. To accomplish this, you need to add label of a META in the HTML file of this article correspondence only. Of the code of this file most begin to resemble a bit:

<html>
<head>
<meta Name= "googlebot" content= "noindex" >
. . .

This paragraph of code can prevent Gu Ge to index this file. Label META is extraordinary and useful, if you are promised to compile individual document only, is not the Robots.txt of complete station. They still promise you to chase page ground to appoint complex visit to control a regulation.

Understanding is more

You can be inHttp://www.robotstxt.org/ And
Gu Ge’s stationmaster helps a center
Find the more and useful information of more concerned Robots.txt, include:


How to construct file of a Robots.txt


To the description of every User-agent that Gu Ge uses


How to use mode to match


How long to want us is ability new capture your Robots.txt file?

We also are in ourStationmaster rich guestA few posts about Robots.txt were kept in, useful to you perhaps. For example:


Use Robots.txt file


Googlebot collect

Here still has the useful detailed account of the robot that engine of a main search uses: Http://www.robotstxt.org/wc/active/html/index.html

Next time…

Be about to roll out: About the card that expatiatory Robots and Metatags use, with the specific example about a few pairs of common circumstances.

Tags: , , , , , , ,

Filed under: Google Blackboard — Wrote by Lees on Wednesday, November 21st, 2007 @ 9:06 am

Tags: , , , , , , ,

Copyright © 2007 Google Adsense College.
Powered by GoogleSchool. All Rights Reserved.