Google announced on their Chromium Blog that they have been working on a common complaint among Chrome users: annoying, intrusive ads. In 2018, they started removing the ads from websites that continually show intrusive ads that violate industry standards. Google also updated their own advertising to ensure they are not selling or serving the kind of ads that users find the most annoying.
Today, the group responsible for developing the Better Ads Standards, the Coalition for Better Ads, announced a new set of standards for ads that show during video content, based on research from 45,000 consumers worldwide.
The Coalition found that three ad experiences that people find to be particularly disruptive on video content that is less than 8 minutes long. They include: long, non-skippable pre-roll ads or groups of ads longer than 31 seconds that appear before a video and that cannot be skipped within the first 5 seconds; Mid-roll ads of any duration that appear in the middle of a video, interrupting the user’s experience; and image or text ads that appear at the top of a playing video and are in the middle 1/3 of the video player window or cover more than 20 percent of the video content.
The Coalition has announced that website owners should stop showing these ads to their site visitors in the next four months. Beginning August 5, 2020, Chrome will expand its user protections and stop showing all ads on sites in any country that repeatedly show these disruptive ads. Google wants people to know that YouTube.com, like other websites with video content, will be reviewed for compliance with the Standards.
Google points those who operate a website that shows ads to the Ad Experience Report. It is a tool that you can use to review your site for compliance with the new ad protections, and that helps publishers to understand if Chrome identified any violating ad experiences on your site.
Overall, I think this change will likely have an effect on those who have ads on their YouTube videos, which could potentially affect their earnings. That said, it appears that these changes are designed to enhance the experience of people want to watch a video – on any website – without being annoyed by intrusive ads.
People who use Chrome as their go-to browser are about to get more control over the audio that autoplays on the websites they visit. Software Engineer Mounir Lamouri posted on the Chromium Blog information about “Unified autoplay”.
Users watch and listen to a lot of media, and autoplay can make it faster and easier to consume on the web. However, one of the most frequent user concerns is unexpected media playback, which can use data, consume power, and make unwanted noise while browsing. To address this, Chrome will be making autoplay more consistent with user expectations and will give users more control over audio.
Chrome 63 will add a new user option to completely disable audio for individual sites. The site muting will persist between browsing sessions. This allows users to customize when and where audio will play.
Starting in Chrome 64, autoplay will be allowed when either the media does not include any audio, or when the user has indicated an interest in the media. These changes will allow autoplay to occur when users want media to play, and will respect users’ wishes when they don’t want media to play.
The Chromium blog post says: “These changes will also unify desktop and mobile web behavior, making web media development more predictable across platforms and browsers.” It sounds to me like these changes will make visiting websites less annoying for people who have not yet started using ad blockers.
Adobe Flash may be dying the slowest death of any software platform that’s ever existed. And it’s about to move even closer to its demise, based on a recent announcement from Google. The search engine and internet services giant has announced that it will stop Flash from loading by default for most websites in its popular Google Chrome web browser.
Google won’t be completely removing or blocking Flash in Chrome. The new default state for the browser will keep Flash from automatically running when a website tries to load a Flash-based player. Instead, Chrome will force websites properly configured with HTML5 players to load those players first. Users will be able to configure the browser to use Flash first if they really want to. Some sites, such as YouTube, Facebook, Twitch, and Amazon will still have Flash enabled by default. But that exemption will only last for one year.
The tech community at large has been watching the slow decline of Flash popularity for about a decade now. In its heyday, Flash was used for everything from in-browser video games and online applications to web-based audio and video players. But when Apple launched its first iPhone, the company was adamant that the device would never, ever support Flash natively. This decision may have led to quicker and wider adoption of HTML5, a web standard that made it easier to deliver rich content thru the internet.
Flash is often derided for its many security issues and its need for constant updates. This move by Google will surely put another nail into Flash’s coffin. I doubt anyone will really be disappointed.
Over the past few days it has come to light that Google was blocking all bit.ly links as if they were malicious. That quickly became a real problem around the web, as many services use the URL shortening service. This made things even harder for folks using the ever-growing Chromebook platform, as there is no way around a problem such as this.
Now, according to security researcher Graham Cluley, as well as other sources, the problem has now been solved. “It appears the issue has now been resolved”, Cluley reports, after initially revealing that “it seems bit.ly has made its way onto Google’s list of sites that aren’t safe to browse to”.
Bit.ly has so far not commented on the problem and it appears there was never a real danger. However, link shortening services have been known to be used to hide the real link in an effort to get a user to a malicious site and bit.ly did suffer an attack earlier this year. That seems to be unrelated to this incident, though.
For now, customers may wish to keep an eye on the service’s blog for any information regarding this incident.
There are times when only hard copy will do but anyone who has tried to print from a tablet will know that it’s not always easy. The main ecosystems from Apple and Google have their own printer strategies with AirPrint and Cloud Print respectively but support is spotty at best. Several printer manufacturers have gone so far as to create their own printer app which really is a pretty poor state of affairs.
Into this gap steps Lantronix with their xPrintServer Cloud Print Edition, the first Google-certified Cloud Print server which lets Android and ChromeOS devices print wirelessly to network and USB printers. Sweet.
The unit is about the size of a smartphone and requires no additional software downloads or printer drivers. It’s simply a case of connecting the device to the network and it automatically finds the printers on the network, making them available to users. The xPrintServer Cloud Print Edition supports any device running Google’s Chrome browser, whether it’s a smartphone, tablet, PC or laptop. Apparently there are over 310 million active users of Chrome, so that’s quite a few people who might want to print. Business users of Google Apps are supported too. Details of the printers supported are available from Lantronix’s website.
This new xPrintServer joins the existing Home and Office Editions which provide print services for iOS devices such as the iPhone and iPad.
The Cloud Print Edition sells for an MSRP of US$149.95 and will ship at the end of February 2014. Pre-orders are being taken now and potential customers can sign up at lantronix.com for more information and availability. Of course, if you are at CES, you can pop round to their stand for a quick demo.
While researching the Philips Hue Android apps, I discovered that currently there is a single Hue app for Chrome. It’s called Hueful and while it’s fairly basic, it deserves a mention as (a) it’s the only app on Chrome but (b) it shows that Chrome can support this kind of hardware-oriented app. Previously I would have discounted Chrome from being an option but Hueful works fine on my Chromebook.
Hueful isn’t a very advanced Hue app, being limited to setting colours of selected lamps and colour cycling. Sometimes lamps need to be told twice to take on a setting but they usually get there in the end.
Hueful is free from the Chrome store.
Google is taking aim at the PC market with its increasingly better offerings of Chromebook hardware. Now the search giant is also touting “family safe” as one of its selling points.
If you are using the beta channel version of Chrome, you now have access to monitor and control what other users access through the browser/operating system. “Let’s say you’ve recently purchased the new HP Chromebook 11 and want to share it with your son. He’ll be able to use your Chromebook as a supervised user. This means once you’ve created a supervised user for him on your Chromebook, you’ll be able to visit chrome.com/manage to review a history of web pages he has visited, determine sites that you want to allow or block, and manage permissions for any blocked websites he has requested to view”, says Google’s Pam Green.
The feature is called “Supervised Users” and has been in testing in the Canary build for sometime. Canary, if you aren’t familiar, is the cutting -edge version of the browser that customers can opt for — at their own risk.