Chrome OS 70, which Google plans to release in the second half of next month, will include native support for SMB file shares, giving it built-in access to files stored on Windows servers. With this, Chrome OS users can add SMB file shares to the Files app and use them to store and load documents. From a report: Currently, using these network resources requires the use of an extension that adds a similar ability to add file shares to the Files app. Google has been working to make Files a more capable application. As well as integrating support for networked files, the company is also experimenting with giving it more access to Android files, something that will streamline the use of Android applications by exposing their data files to Chrome OS apps. The SMB support helps smooth a pain point when mixing Chromebooks with other systems: it makes it easier to use Chrome OS with corporate file servers, home networked storage devices, and of course, Windows PCs. Instead of needing the extra extension to be installed, these things will just work out of the box.

RoccamOccam writes: WebRender, an experimental GPU-based renderer for web content, written in Rust, is now enabled by default for Firefox Nightly users on desktop Windows 10 with Nvidia GPUs. The announcement was made on the mailing list.

Lin Clark provides an excellent overview of WebRender and, states, "with WebRender, we want apps to run at a silky smooth 60 frames per second (FPS) or better no matter how big the display is or how much of the page is changing from frame to frame. And it works. Pages that chug along at 15 FPS in Chrome or today's Firefox run at 60 FPS with WebRender.

In describing the WebRender approach Clark, asks, "what if we removed this boundary between painting and compositing and just went back to painting every pixel on every frame? This may sound like a ridiculous idea, but it actually has some precedent. Modern day video games repaint every pixel, and they maintain 60 frames per second more reliably than browsers do. And they do it in an unexpected way instead of creating these invalidation rectangles and layers to minimize what they need to paint, they just repaint the whole screen."

An anonymous reader shares a report: If you open Edge and search for "Chrome" or "Firefox" using Bing, Edge's default search engine, you'll be presented with a massive banner informing you that "Microsoft Edge is the faster, safer browser on Windows 10 and is already installed on your PC." Four boxes below then show you how Edge lets you browse longer, and faster, offers built-in protection and built-in assistance. If that doesn't stop you, then Microsoft has a new, much nastier trick up its sleeve -- when you go to install Firefox or Chrome it intercepts the action and pops up a window promoting Edge with the same line about how its browser is faster and safer. It then gives you a blue button to click to open Edge, or a grey one you can click to install the browser you actually want to use. Oh, and this window will keep appearing, unless you go into Settings and stop Windows 10 from offering you app "recommendations."
UPDATE (9/15/18): "After massive backlash by users against this move, Microsoft has finally decided to eliminate the warning message," reports Neowin.

Further reading: Creator of Opera Says Google Deliberately Undermined His New Vivaldi Web Browser.

Back in 2014, Mozilla partnered with Bing to translate webpages via Firefox in a similar fashion to Chrome's implementation of Google Translate. The company also added support for Yandex Translate in Firefox 41 in mid-2015, but it went all dark soon after and very few updates were issued. Now, Mozilla is finally starting to add support for Google Translate to the translation engine built into Firefox. gHacks reports: While the feature is not fully functional yet, it is an indicator that Mozilla has not forgotten the translate feature completely. Users who enable the translate functionality in Firefox on about:config will notice that Google is the selected translation engine. Google Translate cannot be used currently in Firefox; the browser throws an error message when you hit the translate button in the UI. Bing and Yandex don't seem to work either at this point in time even though Firefox seems to try and translate the page. The "there has been an error translating this page" error is thrown eventually as well. Google Translate requires API access keys and that is usually only available if companies or users pay for the key. It is unclear if Mozilla plans to make a deal with Google or if users will be required to use their own API keys for the functionality. The latter would surely be very limiting.

"Have you heard of Google AMP? That stands for Accelerated Mobile Pages, and it's a way of making webpages so that they load faster and display more efficiently on mobile devices. Oh, and it puts your website under Google's control."

That's Mac Observer co-founder Bryan Chaffin, linking to an "interesting reading" titled "Google AMP Can Go To Hell." AMP allows Google to basically take over hosting the web as well. The Google AMP Cache will serve AMP pages instead of a website's own hosting environment, and also allow Google to perform their own optimisations to further enhance user experience. As a side benefit, it also allows Google full control over content monetisation. No more rogue ad networks, no more malicious ads, all monetisation approved and regulated by Google. If anything happens that falls outside of the AMP standard's restrictions, the page in question simply becomes AMP-invalid and is ejected from the AMP cache -- and subsequently from Google's results. At that point the page might as well not exist any more....

The easy thing to do is to simply obey. Do what Google says. Accept their proclamations and jump when they tell you to. Or you could fight back. You could tell them to stuff it, and find ways to undermine their dominance. Use a different search engine, and convince your friends and family to do the same. Write to your elected officials and ask them to investigate Google's monopoly. Stop using the Chrome browser. Ditch your Android phone. Turn off Google's tracking of your every move. And, for goodness sake, disable AMP on your website.

Don't feed the monster -- fight it.
Here's how web developer Macieg Ceeglowski put it in 2015. "Out of an abundance of love for the mobile web, Google has volunteered to run the infrastructure, especially the user tracking parts of it." But are these assessments too harsh? Leave your own thoughts in the comment.

Should webmasters resist Google's push for AMP pages?

An anonymous reader quotes ITWire: Google's move to strip out the www in domains typed into the address bar, beginning with version 69 of its Chrome browser, has drawn an enormous amount of criticism from developers who see the move as a bid to cement the company's dominance of the Web. The criticism comes a few days after Chrome's engineering manager Adrienne Porter Felt told the American website Wired that URLs need to be got rid of altogether. The change in Chrome version 69 means that if one types in a domain such as www.itwire.com into the browser search bar, the www portion is stripped out in the address bar when the page is displayed.

When asked about this change in a long discussion thread on a mailing list, a Google staffer wrote: "www is now considered a 'trivial' subdomain, and hiding trivial subdomains can be disabled in flags (will also disable hiding the URL scheme)..." A Google staffer attempted to justify the change, writing: "The subdomains reappear when editing the URL so people type the correct one. They disappear in the steady-state display case because this isn't information that most users need to concern themselves with in most cases..." But this drew an angry response from a poster who questioned the statement "this isn't information that most users need to concern themselves with in most cases" and asked: "According to who? This is simply an opinion stated as a fact...."

This is not the first time Google has been criticised for its moves to change the fundamental structure of URLs. Its Accelerated Mobile Pages, introduced in October 2015, have been criticised for obscuring the original URL of a page and reducing the chances of a reader going back to the original website. Probably for this reason, Apple last year decided that version 11 of iOS would update its Safari browser so that AMP links would be stripped out of an URL when the story was shared... "This is Google making subdomain usage decisions for other entities outside of Google," said yet another poster. "My domains and how subdomains are assigned and delegated are not Google's business to decide."
The controversy moved Slashdot reader Lauren Weinstein to write a new blog post. Its title? "Here's How to Disable Google Chrome's Confusing New URL Hiding Scheme."

UPDATE (9/15/18): Google has announced that after public outcry, they'll return the 'www' to Chrome's URL's -- but only until the next release.

An anonymous reader shares a report: When a group of security researchers reported a popular but allegedly dangerous Mac App Store utility to Apple, noting that it secretly sends "highly sensitive user information" to an "unscrupulous" developer, Apple's response for a full month was surprising: "crickets." But after a cluster of bad press today, Apple finally pulled Yongming Zhang's app Adware Doctor: Anti Malware &Ad from the store.

Three researchers, including former NSA staffer Patrick Wardle, Thomas Reed of Malwarebytes, and "privacy fighter" @privacyis1st, said in a blog post today that they reported Adware Doctor last month for sending a user's Safari, Chrome, Firefox, and App Store browsing histories alongside lists of the Mac's apps and running processes to a server in China. Despite receiving confirmation that Apple received the report, the $5 app remained in the App Store -- where it was ranked the number one paid app across all Mac utilities.

Since the release of Chrome 69 earlier this week, countless of users have gone on social media and Google Product Forums to complain about "blurry" or "fuzzy" text inside Chrome. ZDNet: The blurred font issue isn't only limited to text rendered inside a web page, users said, but also for the text suggestions displayed inside the address bar search drop-down, and Chrome's Developer Tools panel. [...] According to reports, the issue only manifests for Chrome 69 users on Windows. Those who rolled back to Chrome 68 stopped having problems. Users said that changing Chrome, operating system, or screen DPI settings didn't help. "Our team is investigating reports of this behavior. You can find more information in this public bug report," a Google spokesperson said last night after first user complaints started surfacing online. Some users have also expressed concerns over Chrome not showing "trivial subdomains" including www and secure lock sign in the address bar.

The Tor Browser has rolled out a new interface with the release of v8. From a report: The Tor Browser has always been based on the Firefox codebase, but it lagged behind a few releases. Mozilla rolled out a major overhaul of the Firefox codebase in November 2017, with the release of Firefox 57, the first release in the Firefox Quantum series. Firefox Quantum came with a new page rendering engine, a new add-ons API, and a new user interface called the Photon UI. Because these were major, code-breaking changes, it took the smaller Tor team some time to integrate all of them into the Tor Browser codebase and make sure everything worked as intended. The new Tor Browser 8, released yesterday, is now in sync with the most recent version of Firefox, the Quantum release, and also supports all of its features. This means the Tor Browser now uses the same modern Photon UI that current Firefox versions use, it supports the same speed-optimized page rendering engine and has also dropped support for the old XUL-based add-ons system for the new WebExtensions API system used by Chrome, Opera, Vivaldi, Brave, and the rest of the Chromium browsers.

Mark Wilson shares a report from BetaNews: Acknowledging that we are now very much in the streaming age, BitTorrent has launched the first version of Torrent Web. The aim of the browser-based tool is to make torrenting as simple as possible and -- most importantly -- support torrent streaming. It remains to be seen how many people are willing to switch from a dedicated app to a browser-based torrenting experience, but the promise that you can "play while you download, no more staring at progress bars" is certainly alluring. Files are streamable near-instantly as they download, but they are also saved locally in the way you're used to. uTorrent Web is available for Chrome, Firefox, Internet Explorer, Microsoft Edge and Opera and the release finds BitTorrent partnering with Adaware to check torrents for signs of malware, and even download torrents without having to visit websites. Warning: the installer includes (optional) bundleware in the form of Adaware Internet Security and the Opera web browser.

The official Chrome extension for the MEGA.nz file sharing service has been compromised with malicious code that steals usernames and passwords, but also private keys for cryptocurrency accounts, ZDNet reports. From the report: The malicious behavior was found in the source code of the MEGA.nz Chrome extension version 3.39.4, released as an update earlier today. Google engineers have already intervened and removed the extension from the official Chrome Web Store, and also disabled the extension for existing users. According to an analysis of the extension's source, the malicious code triggered on sites such as Amazon, Google, Microsoft, GitHub, the MyEtherWallet and MyMonero web wallet services, and the IDEX cryptocurrency trading platform. The malicious code would record usernames, passwords, and other session data that attackers would need to log in and impersonate users. If the website managed cryptocurrency, the attacker would also extract the private keys needed to access users' funds.

An anonymous reader writes: Google today launched Chrome 69 for Windows, Mac, and Linux, Android, and iOS, just a few days after the browser's 10-year anniversary. The release includes a new design, more powerful omnibox, updated password manager, more accurate autofill, plenty of developer-specific changes, and a slew of security improvements. You can update to the latest version now using Chrome's built-in updater, download it directly from google.com/chrome, or grab it from Google Play and Apple's App Store. Further reading: As Chrome turns 10, Google bets on AI and AR, and Google wants to kill the URL.

As Chrome looks ahead to its next 10 years, the team is mulling its most controversial initiative yet: fundamentally rethinking URLs across the web. From a report: Uniform Resource Locators are the familiar web addresses you use everyday. They are listed in the web's DNS address book and direct browsers to the right Internet Protocol addresses that identify and differentiate web servers. In short, you navigate to WIRED.com to read WIRED so you don't have to manage complicated routing protocols and strings of numbers. But over time, URLs have gotten more and more difficult to read and understand. The resulting opacity has been a boon for cyber criminals who build malicious sites to exploit the confusion. They impersonate legitimate institutions, launch phishing schemes, hawk malicious downloads, and run phony web services -- all because it's difficult for web users to keep track of who they're dealing with. Now, the Chrome team says it's time for a massive change.

"People have a really hard time understanding URLs," says Adrienne Porter Felt, Chrome's engineering Manager. "They're hard to read, it's hard to know which part of them is supposed to be trusted, and in general I don't think URLs are working as a good way to convey site identity. So we want to move toward a place where web identity is understandable by everyone -- they know who they're talking to when they're using a website and they can reason about whether they can trust them. But this will mean big changes in how and when Chrome displays URLs. We want to challenge how URLs should be displayed and question it as we're figuring out the right way to convey identity."

If you're having a tough time thinking of what could possibly be used in place of URLs, you're not alone. Academics have considered options over the years, but the problem doesn't have an easy answer. Porter Felt and her colleague Justin Schuh, Chrome's principal engineer, say that even the Chrome team itself is still divided on the best solution to propose. And the group won't offer any examples at this point of the types of schemes they are considering. The focus right now, they say, is on identifying all the ways people use URLs to try to find an alternative that will enhance security and identity integrity on the web while also adding convenience for everyday tasks like sharing links on mobile devices.

Google first released its Chrome browser 10 years ago today. Marketed as a "fresh take on the browser," Chrome debuted with a web comic from Google to mark the company's first web browser. From a report: It was originally launched as a Windows-only beta app before making its way to Linux and macOS more than a year later in 2009. Chrome debuted at a time when developers and internet users were growing frustrated with Internet Explorer, and Firefox had been steadily building momentum. Google used components from Apple's WebKit rendering engine and Mozilla's Firefox to help bring Chrome to life, and it made all of Chrome's source code available openly as its Chromium project. Chrome focused on web standards and respected HTML5, and it even passed both the Acid1 and Acid2 tests at the time of its release. This was a significant step as Microsoft was struggling to adhere to open web standards with its Internet Explorer browser.

Another significant part of Chrome's first release was the idea of "sandboxing" individual browser tabs so that if one crashed it wouldn't affect the others. This helped improve the speed and stability of Chrome in general, alongside Google's V8 JavaScript engine that the company constantly tweaked to try and push the web forwards. After a decade of Chrome, this browser now dominates as the primary way most people browse the web. Chrome has secured more than 60 percent of browser market share on desktop, and Google's Chrome engineers continue to improve it with new features and push the latest web standards. To mark the milestone, Google said it would make a surprise announcement on Tuesday -- some improvements coming to Chrome.

Ars Technica sees new $600 "premium Chromebooks" Dell, Samsung, HP, and Lenovo as a growing challenge to Windows, proving that Chrome OS is reaching beyond the education market. These $600 machines aren't aimed at those same students. Lenovo reps told us that its new Chromebook was developed because the company was seeing demand for Chromebooks from users with a bit more disposable income. For example, new college students that had used Chrome OS at high school and families who wanted the robustness Chrome OS offers are looking for machines that are more attractive, use better materials, and are a bit faster and more powerful. The $600 machines fit that role.

And that's why Microsoft should be concerned. This demand shows a few things. Perhaps most significantly of all, it shows that Chrome OS's mix of Web applications, possibly extended with Android applications, is good enough for a growing slice of home and education users. Windows still has the application advantage overall, but the relevance of these applications is diminishing as Web applications continue to improve... Second, this demand makes clear that exposure to Chrome OS in school is creating sustained interest in, and even commitment to, the platform. High school students are wanting to retain that familiar environment as they move on. The ecosystem they're a part of isn't the Windows ecosystem. Finally, it also shows that Chrome OS's relatively clean-slate approach (sure, it's Linux underneath, but it's not really being pushed as a way of running traditional Linux software) has advantages that are appealing even to home users. The locked down, highly secure Chrome OS machines require negligible maintenance while being largely immune to most extant malware.

Computerworld suggests a strange strategy for Windows: If you can't beat Chromebook, join Chromebook: The eagle-eyed developers at XDA Developers have spotted a new Google Pixelbook firmware branch. This new code, "eve-campfire," includes a new "Alt OS mode." That "Alt OS"? WIndows 10. From the clues XDA has picked up, this looks as if it will be a real offering and not just an internal project that will never see the light of day. XDA thinks it will be a built-in dual-boot option such as Apple's Boot Camp....

So, why offer Windows on the Chromebook...? I think it's two things. One, Google wants to snag all those users who are still stuck on Windows because of a favorite game or required application. Two (and if I'm right, this is so sneaky of Google), Windows 10 will run like a dog on Chromebooks... would Google rub Microsoft's face in just how much better Chromebooks are than Windows laptops by letting users see for themselves? Sure it would.

VC Fred Wilson writes: I've been thinking about moving from a Mac to a Chromebook as my primary computing device. I have not used desktop software for probably a decade now. The browser is how I do all of my desktop computing. Paying up for a full blown computer when all I need is a browser seems like a waste. And there are some security things that appeal to me about a Chromebook. I like the ability to do two factor authentication on signing into the device, for example. I am curious what advice those of you who use Chromebooks have for me. In the comments section, Kevin C Tofel, a long time journalist and an ex-Googler writes: I'm all on in Chromebooks, currently using a Pixelbook. Base model is fine for my needs, which sound very similar. I am taking some CompSci classes but even from a programming standpoint, the addition of Linux running in containers -- available in Dev and Beta channels now, coming to Stable v. 69 in the coming weeks -- fills that need easily and securely. I don't do a bunch of video editing but I can do audio edits in Audacity for Linux once audio support arrives for Linux on Chrome OS.

I actually use Google for my password management. It's built in to Chrome / Chrome OS and syncs to all devices. Plus, you can always log in and look up passwords at passwords.google.com. Sure if Google is hacked, someone has my passwords, but same can be said for any cloud-based password manager or (if you run 1Password, etc... locally) if someone gains access to your device. I use Google's 2FA to log in to my Google account and even to log in to my Pixelbook - can be done with an authenticator app, SMS or -- my preferred method -- a Yubikey. I'l be buying a Google Titan Security key to replace my Yubikey once they go on sale.

secwatcher shares a report: Last week we reported that Chrome has started displaying alerts more often that suggest users remove programs that are considered incompatible applications with Chrome because they inject code into the browser's processes. These alerts are displayed by Chrome after the browser crashes and suggest the user remove the listed programs because "this application could prevent Chrome from working properly." One of the programs that a lot of users have seen listed in these alerts and is suggested to be removed is the Bitdefender antivirus program as shown above. Having a well known company like Google telling users to remove a security solution is a problem as these programs are important for many users to have installed on their computers in order to protect them from malware, unwanted programs, and malicious websites. Due to these alerts and their suggestion to remove the antivirus software, Bogdan Botezatu, a senior e-threat analyst for Bitdefender, has told Bleeping Computer that as of August 20th, Bitdefender is no longer monitoring Chrome 66 and later with their anti-exploit technology.

While we know that Linux app support is coming to a range of Chromebooks from Lenovo, Acer, Dell and others, a post on the Chromium Gerrit reveals that devices running Linux 3.14 or older will miss out. BetaNews: Chrome OS is able to run Linux apps through the use of containers which help to keep the rest of the operating system safe from harm. As container support requires features that are only found in more recent versions of the Linux kernel, it means that many Chromebooks -- whose kernels are usually not updated -- will not be able to run Linux apps.

Here's the full list of Chromebooks that won't be getting the Linux love: AOpen Chromebase Mini (Feb 2017; tiger, veyron_pinky), AOpen Chromebox Mini (Feb 2017; fievel, veyron_pinky), ASUS Chromebook C201 (May 2015; speedy, veyron_pinky), Acer C670 Chromebook 11 (Feb 2015; paine, auron), Acer Chromebase 24 (Apr 2016; buddy, auron), Acer Chromebook 15 (Apr 2015; yuna, auron), Acer Chromebox CXI2 (May 2015; rikku, jecht), Asus Chromebit CS10 (Nov 2015; mickey, veyron_pinky), Asus Chromebook Flip C100PA (Jul 2015; minnie, veyron_pinky), Asus Chromebox CN62 (Aug 2015; guado, jecht), Dell Chromebook 13 7310 (Aug 2015; lulu, auron), Google Chromebook Pixel (Mar 2015; samus), Lenovo ThinkCentre Chromebook (May 2015; tidus, jecht), Toshiba Chromebookk 2 (Sep 2015; gandof, auron).

Google's curvy tab Material Design update for Chrome will arrive in version 69 of the browser due out in September. From a report: Google flags the upcoming changes in its Enterprise release notes for Chrome 69, which gives a brief mention under browser interface changes to a "new design across all operating systems." Chrome 69, penciled in for stable release on September 4, will also get native Windows 10 notifications, which have been rolling out to users over the past month. Chrome 69 will also progress the long-running project to deprecate Flash Player, which Adobe has announced will reach end of life in 2020. Microsoft, Mozilla, and Apple have similar deprecation timelines for Flash on their desktop browsers. Once ubiquitous, Flash content is now hardly used at all by Chrome users, though Google won't fully remove support until Chrome 87 in 2020. At present, if a user enables Flash for a particular site, they don't need to approve it if they visit the site again. However, in Chrome 69, every time users restart Chrome, they'll need to give permission for sites to use Flash.