Beta Channel Update for Chrome OS

The Beta channel has been updated to Chrome Version: 73.0.3683.84 (Platform version: 11647.101.0) for most Chrome OS devices. This build contains a number of bug fixes, security updates and feature enhancements. A list of changes can be found here

If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using 'Report an issue...' in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Cindy Bayless
Google Chrome

New Drive file suggestions in Chrome launching in beta

What’s changing 

We’re launching a beta program for a new feature that allows users to search for Google Drive files that they have access to when using the Chrome Omnibox (search/URL box). Users in the beta can now search for files in Drive by owner or type, where previously they could only search for a title or URL of a webpage. This feature is similar to what users see when searching for files in Google Drive.

Admins for G Suite Business, Enterprise, Education, Enterprise for Education, and Nonprofits can learn more and apply for the beta here.


Who’s impacted 

Admins only

Why you’d use it 

This feature will give users faster access to the files and data they need while searching in Google Chrome. Users will now be able to see Google Docs, Sheets, Slides, PDFs, and other file type suggestions from both “My Drive” and “Shared with Me” when searching in Chrome browser. This will help people get work done faster.

How to get started 

  • Admins: For more details and how to apply for the beta, see this form. 
  • End Users: No action required. 

Additional details 

This feature will be available to users signed into a Chrome profile on any operating system: Chromebook, Mac, Windows, etc.

Helpful links 

For more details and how to apply for the beta, see this form. 
Learn what sync settings users can manage and how they are managed. 
How to enable or disable chrome Sync. 

Availability 

G Suite editions 
  • Available to G Suite Business, G Suite Enterprise, G Suite for Education, G Suite Enterprise for Education, and G Suite for Nonprofits 
  • Not available to G Suite Basic. 

On/off by default? 
  • This feature will be ON by default for beta participants and can be controlled at the OU level.

Stay up to date with G Suite launches

GNI Subscriptions lab: invigorating the business model for news

Editor’s note: As part of the Google News Initiative, we work with news publishing partners across the world on efforts to help the industry thrive in the digital age. In partnership with FTI Consulting and the Local Media Association (LMA), today we’re launching the GNI Subscriptions Lab for eight publishers in the U.S. and Canada to help them transform their approach to digital subscriptions. A similar effort will launch in Latin America next month. The following post is by the LMA’s President, Nancy Lane.

 While the largest national news publishers have put digital subscriptions at the center of their business transformation, we’ve yet to see a clear template for publications’ success at the metro and local levels. Finding a growth path forward for subscriptions is critical to the very survival of hundreds of newspapers in markets large and small. One local publisher told me that his organization’s existence is being threatened like never before, and that seeing his community lose the kind of journalism they produce is not an option. Another said if we as an industry can’t figure out the digital subscription model, then the end could be near. 

That’s why the Local Media Association teamed up with the Google News Initiative and FTI Consultingto create the GNI Subscriptions Lab. The goal of the lab is to develop a sustainable and thriving business model for newspapers across North America—powered by digital subscriptions.

To get there, we’ve designed a six-month long experience that will address every step of the digital subscriptions process. Eight publishers will be chosen to participate, representing a cross-section of the local news industry, with a mix of both chain-owned and independent community and metro titles. Those chosen must be dedicated to figuring out a subscriptions strategy with buy-in and direct involvement from the highest executives (including the CEO) in their respective companies. They’ll come with open minds, a willingness to experiment and a community spirit built around sharing what they learn along the way. We’re looking to help these eight publishers make significant leaps forward with their subscription businesses, the kinds of leaps that can transform these organizations.

The publishers will undergo a mix of quantitative and qualitative market research, looking at existing and potential reader segments in an attempt to better understand the addressable market, readers willingness to pay and more.  

FTI Consulting will perform a full diagnostic evaluation of each participating publisher across multiple dimensions—including people, process, technology, marketing and content—to benchmark current performance, identify short-term optimization opportunities and recommend longer-term transformation roadmaps. This includes providing a detailed scorecard to show how each publisher sizes up, and a dashboard for measuring ongoing progress.  

During the entire process, the publishers will have support from Google teams that bring expertise in data, technology, product, subscriptions and more. Our businesses will be challenged in new and exciting ways. To have our subscriptions strategies looked at from multiple angles, with all of the powerful tools and resources that they bring, is exactly what’s needed given what’s at stake.

As we see results, we’ll share learnings with the industry at large—including at the LMA-LMC Elevate Summitin September—through experiential learning, playbooks, conference workshops and more. The future of community journalism is indeed at stake. I can’t think of a project more important at this moment in time. This is a powerful group effort, and our expectations are high.

The Google News Initiative, one year in

In the first year of the Google News Initiative, our efforts have centered around a spirit of experimentation, with programs focused on three pillars: working with the news industry to evolve their business models, raising up quality journalism and driving new thinking and approaches in newsrooms. There’s still much to be done, but we remain committed to collaborating with publishers to build a stronger future for journalism.

Empowering sustainable business growth

The business of journalism is undergoing a major transformation as the focus expands from digital advertising to other ways of making money, like subscriptions. Last year, we worked with publishers to design Subscribe with Google (SwG) which makes it easy to subscribe and access news publications across surfaces and devices.

Today, nearly 50 partners from 19 countries have signed up to implement Subscribe with Google and publishers like The Washington Post, the Financial Times, Folha de S. Paulo and Nine Publishing are using the product. Beyond subscriptions we’re expanding to support publishers who monetize using contributions or membership-based models. The Guardian, a leader in the field, is our first partner to test this approach and will help to inform best practices before we fully launch later this spring.

Contribution_News_GoogleAccount.gif


But technology is only one part of the solution. Deeply understanding the needs of readers, building new capabilities and adopting a subscriber-first culture require new approaches and commitments from news publishers. Our new initiative called the GNI Digital Subs Lab will help 14 publishers in North and Latin America transform their approach to digital subscriptions.

Elevating quality journalism

Every day, people come to Google to access quality journalism, but not everyone on the web acts with good intent. Combating misinformation requires forging partnerships with industry organizations, investing in better product solutions, and training journalists on the latest verification tools and technology.

In the last year our News Lab has trained nearly 300,000 journalists in person and online around the world on digital tools for journalism, with a goal to reach 500,000 journalists by 2020. We’ve partnered with the International Fact Check Network and dozens of newsrooms worldwide to quell the spread of misinformation, especially during key times like elections. We’ve supported initiatives like Verificado in Mexico, Comprova in Brazil, CekFakta in Indonesia, FactCheckEU and the journalist training network in India, which included over 100 newsrooms and reached thousands of journalists ahead of key elections—there’s more to come in Australia and Argentina. We’re working with First Draft on their CrossCheck tool, which helps journalists debunk and share information across the world—they’ve already trained hundreds of journalists ahead of the EU elections.

Journalists in London_News Lab workshop.jpg

Journalists attending News Lab workshop at the Worldwide Association of Women Journalists and Writers event in London

Journalists in Bulgaria_News Lab workshop.jpg

Journalists in Bulgaria taking part in a News Lab workshop.

Our fact checking project launched in October 2016 to help people find articles that fact check claims made on the web. Earlier this month we unveiled a feature on YouTube in India that automatically surfaces third-party fact checks from eligible publishers alongside YouTube search results.

We’ll soon be launching two tools to help fact checkers work more efficiently and effectively. The Fact Check Markup tool makes it easy for reporters to put structured data markup into their fact checking content using the open standard ClaimReview, and the Fact Check Explorer helps journalists find fact checking articles for various topics through a simple search function. We’re also opening up APIs for these tools to help developers build their own applications to assist fact checkers across the world.

Beyond our products, we’re working to tackle the intentional spread of misinformation across Search, News, YouTube and our advertising systems. In the coming weeks we’ll launch a “How News Works” site, communicating the values that shape our approach.

And to teach the next generation the difference between fact and fiction online we launched a $10 million global media literacy campaign with Google.org last year. In the U.S., MediaWise—led by the Poynter Institute—has trained 6,000 teens, launched a Teen Fact Check Network and partnered with YouTube creators like John Green and Destin Sandlin on digital literacy programming.

In Europe we’re supporting Media Veritas to promote media literacy among the most vulnerable communities in Portugal, Student View in the UK to expand its school newsroom program and, in Finland, the Mannerheim Child Welfare Association to run 150 local events focused on digital well being.

New technology for news organizations

To help news organizations around the world experiment with new formats, we’ve given more than $5 million in audio innovation grants and launched a $25 million program with YouTube that funded 87 publishers to develop sustainable video operations.

TheGNI Cloud program, aimed at small and midsize news organizations, has provided over 6,000 free GSuite licenses and around $1 million in Google Cloud Credits to almost 100 publishers worldwide. Today we’re expanding the program to train 14 news organizations—including Clarín in Argentina and Nikkei in Japan—in machine learning to develop use cases around personalization and content tagging that may ultimately become real products.

Newspack is a partnership with Automattic and Wordpress.com to build a fast, secure, low-cost publishing system tailor-made to the needs of small and medium-sized newsrooms. Next week  the publications selected for phase one of the program will be unveiled.

This is just a snapshot of our efforts to build a healthy future for journalism—a vision that would not be possible without the collaboration and partnership of publishers from across the world.

Reducing the Need for Labeled Data in Generative Adversarial Networks



Generative adversarial networks (GANs) are a powerful class of deep generative models.The main idea behind GANs is to train two neural networks: the generator, which learns how to synthesise data (such as an image), and the discriminator, which learns how to distinguish real data from the ones synthesised by the generator. This approach has been successfully used for high-fidelity natural image synthesis, improving learned image compression, data augmentation, and more.
Evolution of the generated samples as training progresses on ImageNet. The generator network is conditioned on the class (e.g., "great gray owl" or "golden retriever").
For natural image synthesis, state-of-the-art results are achieved by conditional GANs that, unlike unconditional GANs, use labels (e.g. car, dog, etc.) during training. While this makes the task easier and leads to significant improvements, this approach requires a large amount of labeled data that is rarely available in practice.

In "High-Fidelity Image Generation With Fewer Labels", we propose a new approach to reduce the amount of labeled data required to train state-of-the-art conditional GANs. When combined with recent advancements on large-scale GANs, we match the state-of-the-art in high-fidelity natural image synthesis using 10x fewer labels. Based on this research, we are also releasing a major update to the Compare GAN library, which contains all the components necessary to train and evaluate modern GANs.

Improvements via Semi-supervision and Self-supervision
In conditional GANs, both the generator and discriminator are typically conditioned on class labels. In this work, we propose to replace the hand-annotated ground truth labels with inferred ones. To infer high-quality labels for a large dataset of mostly unlabeled data, we take a two-step approach: First, we learn a feature representation using only the unlabeled portion of the dataset. To learn the feature representations we make use of self-supervision in the form of a recently introduced approach, in which the unlabeled images are randomly rotated and a deep convolutional neural network is tasked with predicting the rotation angle. The idea is that the models need to be able to recognize the main objects and their shapes in order to be successful on this task.
An unlabeled image is randomly rotated and the network is tasked with predicting the rotation angle. Successful models need to capture semantically meaningful image features which can then be used for other vision tasks.
We then consider the activation pattern of one of the intermediate layers of the trained network as the new feature representation of the input, and train a classifier to recognize the label of that input using the labeled portion of the original data set. As the network was pre-trained to extract semantically meaningful features from the data (on the rotation prediction task), training this classifier is more sample-efficient than training the entire network from scratch. Finally, we use this classifier to label the unlabeled data.

To further improve the model quality and training stability we encourage the discriminator network to learn meaningful feature representations which are not forgotten during training by means of an auxiliary loss we introduced previously. These two advancements, combined with large-scale training lead to state-of-the-art conditional GANs for the task of ImageNet synthesis as measured by the Fréchet Inception Distance.
Given a latent vector the generator network produces an image. In each row, linear interpolation between the latent codes of the leftmost and the rightmost image results in a semantic interpolation in the image space.
Compare GAN: A Library for Training and Evaluating GANs
Cutting-edge research on GANs is heavily dependent on a well-engineered and well-tested codebase, since even replicating prior results and techniques requires a significant effort. In order to foster open science and allow the research community benefit from recent advancements, we are releasing a major update of the Compare GAN library. The library includes loss functions, regularization and normalization schemes, neural architectures, and quantitative metrics commonly used in modern GANs, and now supports:
Conclusions and Future Work
Given the growing gap between labeled and unlabeled data sources, it is becoming increasingly important to be able to learn from only partially labeled data. We have shown that a simple yet powerful combination of self-supervision and semi-supervision can help to close this gap for GANs. We believe that self-supervision is a powerful idea that should be investigated for other generative modeling tasks.

Acknowledgments
Work conducted in collaboration with colleagues on the Google Brain team in Zürich, ETH Zürich and UCLA. We would like to thank our paper co-authors Michael Tschannen, Xiaohua Zhai, Olivier Bachem and Sylvain Gelly for their input and feedback. We would like to thank Alexander Kolesnikov, Lucas Beyer and Avital Oliver for helpful discussion on self-supervised learning and semi-supervised learning. We would like to thank Karol Kurach and Marcin Michalski for their major contributions to the Compare GAN library. We would also like to thank Andy Brock, Jeff Donahue and Karen Simonyan for their insights into training GANs on TPUs. The work described in this post also builds upon our work on “Self-Supervised Generative Adversarial Networks” with Ting Chen and Neil Houlsby.

Source: Google AI Blog


Reflecting on Google Code-in 2018

Google Code-in (GCI), our contest introducing 13-17 year olds to open source software development, wrapped up last December with impressive numbers: 3,124 students from 77 countries completed an impressive 15,323 tasks!

These students spent 7 weeks working online with 27 open source organizations, writing code, writing and editing documentation, designing UI elements and logos, conducting research, developing videos teaching others about open source software, as well as finding (and fixing!) hundreds of bugs.

Overview

  • 2,164 students completed three or more tasks (earning a Google Code-in 2018 t-shirt)
  • 17% of students were girls
  • 23% of the participants from the USA were girls
  • 79% of students were first time participants in GCI
  • We saw very large increases in the number of students from Austria, Indonesia, Malaysia, Pakistan, and Taiwan

Student Age

Participating Schools

Students from 1,673 schools competed in this year’s contest. Many students learn about GCI from their friends or teachers and continue to spread the word to their classmates. This year the 5 schools with the most students completing tasks in the contest were:
School Name Number of Student Participants Country
Dunman High School 110 Singapore
Indus E.M High School 73 India
Sacred Heart Convent Senior Secondary School 69 India
Amity International School Sec-46 Gurgaon 36 India
Bhartiya Vidya Bhavan Vidyashram Pratap Nagar 27 India

Countries

We are pleased to have 9 countries with first time Winners and Finalists. Winners from Georgia, Macedonia, Philippines, South Africa and Spain, and Finalists from Israel, Luxembourg, Nepal and Pakistan.

The chart below displays the 10 countries with the most students completing at least 1 task.

What's Next

In June we will welcome all 54 grand prize winners to the San Francisco Bay Area for a fun-filled trip. The trip includes the opportunity for students to meet with one of the mentors they worked with during the contest. Students will also take part in an awards ceremony, meet with Google engineers to hear about new and exciting projects, tours of the Google campuses and a fun day exploring San Francisco.

We are thrilled that Google Code-in was so popular this year. We hope to continue to grow and expand this contest in the future to introduce even more teenagers to the world of open source software development.

Thank you again to the heroes of this program: the 789 mentors from 57 countries that guided students through the program and welcomed them into their open source communities.

By Saranya Sampat, Google Open Source

Building a safer internet, one secure domain at a time

Do you lock your doors when you're not home or when you’re sleeping at night? Your home protects everything and everyone that lies within it—whether that’s your family, pets or belongings—and a door is the most direct way for a criminal to access your home. Locking your door is the simplest thing you can do to keep safe. Similarly, when you’re browsing the web, there’s one key thing that helps keep you and your information safe and “locked” up.


HTTPS is a certificate that works just like the lock on your front door at home. By “locking” your connection to a website, it helps prevent interception or alteration of content on the site you’re visiting. We want every website to have a lock on it. That’s why Google Registry created safe.page: so you can understand the most direct steps you can take to keep yourself and others safe while browsing the internet.

Visit safe.page to learn how to read a URL (to avoid phishing attacks) and the importance of a secure connection (especially when sharing sensitive info like credit cards and passwords).

Build safely, get rewarded

That’s not all we’re doing to support HTTPS. We're also teaming up with WordPress to make it easy for anyone to build a secure website. They make building secure websites a snap by automatically installing SSL certificates at no cost for domains they host. If HTTPS is locking your online information safely, an SSL certificate acts like the actual lock on the door.


If you’ve been thinking of building a website, now’s a good time to get started: We're running a contest for the best sites created through April 30, 2019. Nine winners will be selected based on their website’s user experience, user interface, originality, design and content clarity. Winners will receive a Pixel 3 phone or equivalent prize and the opportunity to be featured on one of Google Registry's websites (get.page, get.app and get.dev). Entering the competition is simple:

  1. Register your .page, .app or .dev domain. All three extensions are secure by default (registered domains only work with an SSL certificate). You can register your domain through your preferred registrar.
  2. Build your website. You can get started building your site on WordPress.com and save 25 percent using the promo code SAFE_A24F at checkout. (The offer is valid until April 30, 2019.) Websites created in other ways on .app, .page and .dev are also eligible for the contest.
  3. Learn more about the contest rules here, including eligibility restrictions, prize details and entry deadlines. Submit your website to the contest at safe.page.

That’s it! Regardless of whether you create your own secure website, we encourage everyone to visit safe.page to learn the fundamentals of keeping your information safe. Good luck and thanks for doing your part to build a safer internet!

Supporting choice and competition in Europe

For nearly a decade, we’ve been in discussions with the European Commission about the way some of our products work. Throughout this process, we’ve always agreed on one thing一that healthy, thriving markets are in everyone’s interest.

A key characteristic of open and competitive markets一and of Google’s products一is constant change. Every year, we make thousands of changes to our products, spurred by feedback from our partners and our users. Over the last few years, we’ve also made changes一to Google Shopping; to our mobile apps licenses; and to AdSense for Search一in direct response to formal concerns raised by the European Commission.  

Since then, we’ve been listening carefully to the feedback we’re getting, both from the European Commission, and from others. As a result, over the next few months, we’ll be making further updates to our products in Europe.

Since 2017, when we adapted Google Shopping to comply with the Commission’s order, we’ve made a number of changes to respond to feedback. Recently, we’ve started testing a new format that gives direct links to comparison shopping sites, alongside specific product offers from merchants.  

On Android phones, you’ve always been able to install any search engine or browser you want, irrespective of what came pre-installed on the phone when you bought it. In fact, a typical Android phone user will usually install around 50 additional apps on their phone.

After the Commission’s July 2018 decision, we changed the licensing model for the Google apps we build for use on Android phones, creating new, separate licenses for Google Play, the Google Chrome browser, and for Google Search. In doing so, we maintained the freedom for phone makers to install any alternative app alongside a Google app.

Now we’ll also do more to ensure that Android phone owners know about the wide choice of browsers and search engines available to download to their phones. This will involve asking users of existing and new Android devices in Europe which browser and search apps they would like to use.

We’ve always tried to give people the best and fastest answers一whether direct from Google, or from the wide range of specialist websites and app providers out there today.  These latest changes demonstrate our continued commitment to operating in an open and principled way.

Source: Android


An updated plan & resources for upcoming changes to Groups settings

What’s changing 

Based on your feedback following our previous announcement, Changes to Google Groups settings starting May 6, 2019, we’re making the following changes:


  • Additional improvements to the Groups Settings API to help you plan for and manage the changes (see more details below). 
  • “Post as the group” will remain a separate setting - it will not be merged as we previously stated. 
  • “New member posts are moderated” will remain an option for moderation - it will not be deprecated as we previously stated. 
  • “Take topics” will be merged into the content metadata settings


To help you plan for these changes, we’re also sharing a Google Sheet which can help identify what the new settings will be for a group. In addition, we’re changing the rollout schedule so the new settings will start to take effect in Scheduled Release domains on June 3, four weeks after Rapid Release domains.

Use our Help Center to see details of these changes and see how you can prepare for the update.

Who’s impacted 

Admins and end users

Why you’d use it 

We hope these resources will help you better understand and prepare for the changes to Groups settings.

How to get started 




Additional details 

Groups API improvements 
On March 25th, 2019, we’ll be updating the Groups Settings API. These updates align the API with the product changes we’re making (outlined in our previous announcement and this post) and mean it’s easier to use the API to prepare. API updates include:


  • All settings that are to-be merged will be exposed via the API. This means you can audit your current groups via API, and make changes to ensure new settings are inferred as you want them to be. 
  • New merged settings will be exposed via the API. This means you can query the new merged settings and ensure they are going to be inferred as expected. Note that It will be read-only (i.e. inferred value) until launch, at which point it will also support write. 
  • New bit for custom roles exposed. If you use custom roles, API queries may return incorrect values. The new bit will highlight if a group uses custom roles for one of the merged settings and so will help you identify groups that require manual review. 
  • New bit for collaborative inbox exposed. We will expose a new bit that represents whether collaborative inbox will be enabled for a group. If you expect your group to have collaborative inbox functionality (e.g. topic assignment), ensure that this bit is true. You may do this by enabling any of the collaborative inbox features. Note that it will be read-only (i.e. inferred value) until launch, at which point it will also support write. 
  • New bit for who can discover group exposed. We will expose a new bit that represents who the group will be visible to. This setting will replace show in group directory. Note that it will be read-only (i.e. inferred value) until launch, at which point it will also support write. 


See our Cloud blog post for more details on these API changes and how to use them.

“Post as the group” will not be merged into the content moderator setting 
Previously we stated that this setting would be merged. However, you told us that it was valuable and we should keep it separate, so we’re updating the plans and will not merge it.

“New member posts are moderated” will continue to be supported. 
The “New member posts are moderated” setting, exposed in the API as MODERATE_NEW_MEMBERS, will continue to be supported as a value for moderation.

“Take topics” will be merged with content metadata 
We previously suggested that “Take topics” would remain a standalone setting. However, this will now be merged as part of the content metadata settings.

New worksheet to help visualize changes
We’ve created this Google Sheet which will show you what the new settings will be for any group if you input the current settings. This can help you check the settings will be inferred as you want them.

Helpful links 




Availability 

Rollout details 


G Suite editions 
Available to all G Suite editions.

On/off by default? 
This feature will be ON by default.
Stay up to date with G Suite launches

Minor updates related to the Activity Dashboard in Editors and the Admin console

Quick launch summary 

We’re making two minor updates to verbiage found in the Activity Dashboard in Editors and related settings within the Admin console. As we launch more features to the Activity Dashboard, these updates will help keep things clear for both admins and end users.

In the Admin console: 
In the Activity dashboard settings, where it previously read “Access to activity dashboard” on the left hand navigation, it will now read “Access to view history.”



From here, Admins can set the ability for users to access Viewers and Viewer trend activity in the dashboard to ON/OFF. To learn more about file activity visibility, see this article in the Help Center.

In Editors: 
Within the Activity dashboard, the “View time” tab has been renamed to “Viewers.” From this tab, document owners can see the last time users with Edit access viewed the file and take action to follow-up. To learn more about view history in Docs, Sheets, and Slides, see this Help Center article. 

We’re also changing the icon for the Viewers tab — previously it was a clock, now it will be a person. This change is to better indicate the purpose of this tab, which is viewer history, not time viewers spent in the document.



Availability 

Rollout details
G Suite editions 
  • Available to all G Suite Editions.

Stay up to date with G Suite launches