Data and code open sourced from Google’s Renewable Energy Cheaper than Coal project
January 30th, 2012 | by Stephanie Taylor | published in Google Open Source, Uncategorized
Google’s RE
January 30th, 2012 | by Stephanie Taylor | published in Google Open Source, Uncategorized
Google’s RE
January 30th, 2012 | by A Googler | published in Google Blog, Uncategorized
Our business at Google is rooted in STEM and CS, so we’re passionate about supporting organizations that are expanding access to these fields, especially for students who might not have the opportunity otherwise. The annual Google Roots in Scien…
January 30th, 2012 | by Jay | published in Google Online Security
Posted by Adam Dawes, Product Manager
Email phishing, in which someone tries to trick you into revealing personal information by sending fake emails that look legitimate, remains one of the biggest online threats. One of the most popular methods that scammers employ is something called domain spoofing. With this technique, someone sends a message that seems legitimate when you look at the “From” line even though it’s actually a fake. Email phishing is costing regular people and companies millions of dollars each year, if not more, and in response, Google and other companies have been talking about how we can move beyond the solutions we’ve developed individually over the years to make a real difference for the whole email industry.
Industry groups come and go, and it’s not always easy to tell at the beginning which ones are actually going to generate good solutions. When the right contributors come together to solve real problems, though, real things happen. That’s why we’re particularly optimistic about today’s announcement of DMARC.org, a passionate collection of companies focused on significantly cutting down on email phishing and other malicious mail.
Building upon the work of previous mail authentication standards like SPF and DKIM, DMARC is responding to domain spoofing and other phishing methods by creating a standard protocol by which we’ll be able to measure and enforce the authenticity of emails. With DMARC, large email senders can ensure that the email they send is being recognized by mail providers like Gmail as legitimate, as well as set policies so that mail providers can reject messages that try to spoof the senders’ addresses.
We’ve been active in the leadership of the DMARC group for almost two years, and now that Gmail and several other large mail senders and providers — namely Facebook, LinkedIn, and PayPal — are actively using the DMARC specification, the road is paved for more members of the email ecosystem to start getting a handle on phishing. Our recent data indicates that roughly 15% of non-spam messages in Gmail are already coming from domains protected by DMARC, which means Gmail users like you don’t need to worry about spoofed messages from these senders. The phishing potential plummets when the system just works, and that’s what DMARC provides.
If you’re a large email sender and you want to try out the DMARC specification, you can learn more at the DMARC website. Even if you’re not ready to take on the challenge of authenticating all your outbound mail just yet, there’s no reason to not sign up to start receiving reports of mail that fraudulently claims to originate from your address. With further adoption of DMARC, we can all look forward to a more trustworthy overall experience with email.
January 30th, 2012 | by The Gmail Team | published in Gmail (Google Mail), Uncategorized
Posted by Adam Dawes, Product ManagerEmail phishing, in which someone tries to trick you into revealing personal information by sending fake emails that look legitimate, remains one of the biggest online threats. One of the most popular methods that sc…
January 29th, 2012 | by Scott Knaster | published in Google Code
By Rania Hadi, MENA Outreach Manager
View this post in Arabic
Building on a year packed with g|days throughout the Middle East and North Africa, today we are announcing Google MENA’s first 2012 event to kick off the new year. On March 24-25, Google, in collaboration with Badir Technology Incubator, will be hosting our second event in the Kingdom: g|saudi arabia 2.0.
We’re coming to Jeddah with a host of fresh sessions on all things technology and business. Google engineers, product managers, and business leaders will be there to not only deliver trainings but will be available for any questions, ideas, or discussions you may want to have. We’re also planning some new formats: hands-on workshops, dedicated sessions for women in technology, and chances to showcase Saudi’s finest developer talent.
So if you are a developer, programmer, IT professional, entrepreneur, or small business/start-up, you won’t want to miss this event! If you need more convincing, have a look at the fun, enthusiasm and energy from last year.
Rania Hadi has been with Google since 2004 and now works on Outreach in MENA. She focuses on building relationships and promoting Google technologies with the developer and tech communities.
Posted by Scott Knaster, Editor
January 27th, 2012 | by Stephanie Taylor | published in Google Open Source, Uncategorized
Drupal is an open source content management system with thousands of active community members behind it. A popular solution for both small and large scale websites, Drupal is extremely flexible and offers thousands of add-on modules. Drupal’s u…
January 27th, 2012 | by Scott Knaster | published in Google Code
By Scott Knaster, Google Code Blog Editor
Everybody likes a faster web, and that theme has been evident this week here on Google Code Blog. On Monday, Yuchung Cheng wrote about Google’s research into making TCP faster through various proposals and experiments. Yesterday, Roberto Peon and Will Chan blogged about SPDY (pronounced speedy), Google’s protocol for speeding up the web’s application layer historically handled by HTTP. In related news this week, the chairman of the HTTPbis Working Group announced support for SPDY in a public post.
At Google, these projects are part of our Make the Web Faster initiative, although TCP improvements and SPDY are efforts of the whole community. Even if you’re not working on TCP or SPDY, you can find lots of useful resources at our Make the Web Faster site. For example, there are articles on compression, caching, metrics, and more, a set of tools for measuring and optimizing pages, and several discussion forums for communicating with other interested folks.
Sometimes stronger is more important than faster. Scientists looking to improve the durability of machinery have been studying the yellow fattail scorpion, which uses bumps on its back to resist damage from sandstorms. Researchers hope to use the scorpion’s design to create erosion-resistant surfaces for blades, pipes, and similar parts. Or maybe they’ll make machines that look like giant yellow scorpions.
Finally, take a step back from everything on Earth and have a look at NASA’s latest “Blue Marble” images of our planet. We have a beautiful home.
Let’s say this fast: Fridaygram posts are just for fun. Fridaygrams are designed for your Friday afternoon and weekend enjoyment. Each Fridaygram item must pass only one test: it has to be interesting to us nerds. That definitely includes speed, space, and scorpions.
January 27th, 2012 | by Adam Swidler | published in Google Apps, Google Enterprise, Uncategorized
Posted by Patrick Ryan, Policy Counsel, Open InternetLast year, we were excited about the effort initiated by the U.S. government to promote cloud adoption through the Cloud First initiative. Through this initiative, the federal government declared tha…
January 26th, 2012 | by Google Public Policy Blog | published in Google Public Policy, Uncategorized
Posted by Betsy Masiello, Policy Manager A lot has been said about our new privacy policy. Some have praised us for making our privacy policy easier to understand. Others have asked questions, including members of Congress, and that’s understandable…
January 26th, 2012 | by Vanessa Schneider | published in Google Earth, Uncategorized
(Cross-posted on the Small Business Blog.)When we initially announced the Business Photos pilot program, we wanted to give business owners an easy way to get customers in the door online using interactive, high-quality, 360-degree images of places on G…
January 26th, 2012 | by Inside AdSense Team | published in Google Adsense, Uncategorized
(Originally posted on the Google+ Platform Blog, cross posted on the Webmaster Central Blog)UPDATE (2/2/12): The new Google+ badge is now out of preview and available to all users on all sites. When we launched Google+ pages in November, we also releas…
January 26th, 2012 | by The App Engine Team | published in Google App Engine
Today’s post is contributed by our Summer 2011 team intern, Chris Bunch. Chris did some great work on our Logs and MapReduce APIs and is also the first “App Engine Triple Crown” winner for developing the Experimental Logs Reader API in Python, …
January 26th, 2012 | by Scott Knaster | published in Google Code
![]() |
Will |
![]() |
Roberto |
By Roberto Peon and Will Chan, Software Engineers
Cross-posted with the Chromium Blog
In the two years since we announced SPDY, we’ve been working with the web community on evolving the spec and getting SPDY deployed on the Web.
Chrome, Android Honeycomb devices, and Google’s servers have been speaking SPDY for some time, bringing important benefits to users. For example, thanks to SPDY, a significant percentage of Chrome users saw a decrease in search latency when we launched SSL-search. Given that Google search results are some of the most highly optimized pages on the internet, this was a surprising and welcome result.
We’ve also seen widespread community uptake and participation. Recently, Firefox has added SPDY support, which means that soon half of the browsers in use will support SPDY. On the server front, nginx has announced plans to implement SPDY, and we’re actively working on a full featured mod-spdy for Apache. In addition, Strangeloop, Amazon, and Cotendo have all announced that they’ve been using SPDY.
Given SPDY’s rapid adoption rate, we’re working hard on acceptance tests to help validate new implementations. Our best practices document can also help website operators make their sites as speedy as possible.
With the help of Mozilla and other contributors, we’re pushing hard to finalize and implement SPDY draft-3 in early 2012, as standardization discussions for SPDY will start at the next meeting of the IETF.
We look forward to working even more closely with the community to improve SPDY and make the Web faster!
To learn more about SPDY, see the link to a Tech Talk here, with slides here.
Roberto Peon and Will Chan co-lead the SPDY effort at Google. Roberto leads SPDY server efforts and continues to tell people to be unafraid of trying to change the world for the better. Will works on the Chrome network stack and leads the Chrome SPDY efforts. Outside of work, Will enjoys traveling the world in search of cheap beer and absurd situations.
Posted by Scott Knaster, Editor
January 26th, 2012 | by Tim Bray | published in Google Android
[This post is by Scott Main, lead tech writer for developer.android.com. — Tim Bray]Before Android 3.0 (Honeycomb), all Android-powered devices included a dedicated Menu button. As a developer, you could use the Menu button to disp…
January 26th, 2012 | by A Googler | published in Google Blog, Uncategorized
Googlers are the types who never really leave the classroom. Guest speakers come to campus to give talks on subjects ranging from fiction to physics. Diverse groups of people work together to understand and solve big problems while groups of Googlers e…