An anonymous reader shares a report: Project Campfire turned up in the Chromium world this past August. The intent was to let a Chromebook boot not just into Chrome OS but directly into another operating system such as Linux or Windows. I thought the latter was a positive outcome since it would allow Chromebooks to natively run Windows desktop apps on a Chromebook, and add value to devices. Unfortunately, the project is shutting down. Spotted in code, there are comments and code removals that make it clear Project Campfire is being deprecated.

sfcrazy writes: Mark Shuttleworth, founder and CEO of Canonical, summed it in a few words: "I think the bigger challenge has been that we haven't invented anything in the Linux that was like deeply, powerfully ahead of its time." He also said that "if in the free software community we only allow ourselves to talk about things that look like something that already exists, then we're sort of defining ourselves as a series of forks and fragmentations." He added that it seems the desktop Linux people want to be angry at something. We wanted to do amazing things with Unity but the community won't let us do it, so here we are. He also commended Google folks for what they have built for Chrome OS.

"2019 is truly, finally shaping up to be the year of Linux on the desktop," writes PC World's senior editor, adding "Laptops, too!" But most people won't know it. That's because the bones of the open-source operating system kernel will soon be baked into Windows 10 and Chrome OS, as Microsoft and Google revealed at their respective developer conferences this week... Between lurking in Windows 10 and Chrome OS, and the tiny portion of actual Linux distro installs, pretty much any PC you pick up will run a Linux kernel and Linux software. Macs won't, but it's based on a Unix-like BSD system that already runs many Linux apps with relative ease (hence Apple's popularity with developers).

You have to wonder where that leaves proper Linux distributions like Ubuntu and Linux Mint, though. They already suffer from a minuscule user share, and developers may shift toward Windows and Chrome if the Linux kernels in those operating systems get the same job done. Could this fruit wind up poisonous over the long term? We'll have to see. That said, Linux is healthier than ever. The major distros are far more polished than they used to be, with far fewer hardware woes than installs of yesteryear. You can even get your game on relatively well thanks to Valve's Proton technology, which gets many (but not all) Steam games working on Linux systems. And hey, Linux is free.

Normal users may never be aware of it, but 2019 may finally be the year of Linux on the desktop -- just not Linux operating systems on the desktop.

An anonymous reader quotes a report from ZDNet: At the I/O 2019 developer conference earlier this week, Google launched a new technology called Portals that aims to provide a new way of loading and navigating through web pages. According to Google, Portals will work with the help of a new HTML tag named . This tag works similarly to classic tags, allowing web developers to embed remote content in their pages. Google says portals allow users to navigate inside the content they are embedding --something that iframes do not allow for security reasons. Furthermore, portals can also overwrite the main URL address bar, meaning they are useful as a navigation system, and more than embedding content -- the most common way in which iframes are used today.

For example, engineers hope that when a user is navigating a news site, when they reach the bottom of a story, related links for other stories are embedded as portals, which the user can click and seamlessly transition to a new page. The advantage over using Portals over classic links is that the content inside portals can be pre-loaded while the user scrolls through a page, and be ready to expand into a new page without having the user wait for it to load. In a demo, you can see that Portals allow users to watch/listen to embedded content and then transition seamlessly to its origin page, where they could leave comments or open other media.

At Google's I/O developer conference this past week, Android and Chrome chief Hiroshi Lockheimer offered some rare insight into Fuchsia, albeit at a very high level, in front of public audiences. The Verge reports: What we do know about Fuchsia is that it's an open source project, similar to AOSP, but could run all manner of devices, from smart home gadgets to laptops to phones. It's also known to be built on an all-new, Google-built kernel called "zircon," formerly known as "magenta," and not the Linux kernel that forms the foundation of Android and Chrome OS.

"We're looking at what a new take on an operating system could be like. And so I know out there people are getting pretty excited saying, 'Oh this is the new Android,' or, 'This is the new Chrome OS,'" Lockheimer said. "Fuchsia is really not about that. Fuchsia is about just pushing the state of the art in terms of operating systems and things that we learn from Fuchsia we can incorporate into other products." He says the point of the experimental OS is to also experiment with different form factors, a hint toward the possibility that Fuchsia is designed to run on smart home devices, wearables, or possibly even augmented or virtual reality devices. "You know Android works really well on phones and and you know in the context of Chrome OS as a runtime for apps there. But Fuchsia may be optimized for certain other form factors as well. So we're experimenting." Lockheimer provided some additional details at a separate Android fireside chat held at Google I/O today. "It's not just phones and PCs. In the world of [the Internet of Things], there are increasing number of devices that require operating systems and new runtimes and so on. I think there's a lot of room for multiple operating systems with different strengths and specializations. Fuchsia is one of those things and so, stay tuned," he told the audience.

At Google I/O in Mountain View, Google said "all devices [Chromebook] launched this year will be Linux-ready right out of the box." From a report: In case you've missed it, last year, Google started making it possible to run desktop Linux on Chrome OS. Since then, more Chromebook devices are able to run Linux. Going forward, all of them will be able to do so, too. Yes. All of them. ARM and Intel-based.

Google plans to add support for two new privacy and security features in Chrome, namely same-site cookies and anti-fingerprinting protection. From a report: The biggest change that Google plans to roll out is in regards to how it treats cookie files. These new controls will be based on a new IETF standard that Chrome and Mozilla developers have been working on for more than three years. This new IETF specification describes a new attribute that can be set inside HTTP headers. Called "SameSite," the attribute must be set by the website owner and should describe the situations in which a site's cookies can be loaded.

[...] Google engineers also announced a second major new privacy feature for Chrome. According to Google, the company plans to add support for blocking certain types of "user fingerprinting" techniques that are being abused by online advertisers. Google didn't go into details of what types of user fingerprinting techniques it was planning to block. It is worth mentioning that there are many, which range from scanning locally installed system fonts to abusing the HTML5 canvas element, and from measuring a user's device screen size to reading locally installed extensions.

Google Duplex, Google's AI chat agent that can arrange appointments over the phone, will soon expand to more places -- namely the web. From a report: Today at I/O 2019, Google announced Duplex on the web, which will handle things like rental car bookings and movie tickets. "We want to build a more helpful Google for everyone," said CEO Sundar Pichai onstage in Mountain View, California. "We're going to be thoughtful [about this]." When Duplex on the web debuts, you'll be able to issue Google Assistant a command like "Book me a car from Hertz." That command will navigate to the relevant web page and automatically fill in details like your name, payment information, car preferences, trip dates (using information from Gmail and Chrome autofill), and more. Throughout the process, you'll see a progress bar. And whenever Duplex needs more information, like a price or seat selection, it'll pause and prompt you to make a selection. Once you're finished, a tap of the confirmation button will beam a receipt to your inbox. It'll launch later this year on Android phones.

In a blog post detailing new features coming to Edge, Microsoft has started teasing what Edge will look like on macOS. The Verge reports: During the company's Build 2019 developer conference, Microsoft is announcing new features for Edge on Windows and teasing the upcoming macOS release. We understand that the release will be available very soon, and Mac users should be able to access both the Canary and Dev builds of Edge just like Windows. Microsoft's implementation of Chromium on Edge has so far seen good performance improvements and reliability on Windows. It's not clear if we'll see similar improvements on the macOS side versus Chrome, but at least it gives Mac users another Chromium option with some Microsoft services and sync integration. MacRumors notes that Edge "will be Microsoft's first web browser on the Mac since Internet Explorer received its last feature update nearly 16 years ago."

Google is set to launch new tools to limit the use of tracking cookies, a move that could strengthen the search giant's advertising dominance and deal a blow to other digital-marketing companies, WSJ reported Monday, citing people familiar with the matter. [Editor's note: the link may be paywalled; alternative source.] From the report: After years of internal debate, Google could as soon as this week roll out a dashboard-like function in its Chrome browser that will give internet users more information about what cookies are tracking them and offer options to fend them off, the people said. This is a more incremental approach than less-popular browsers, such as Apple's Safari and Mozilla's Firefox, which introduced updates to restrict by default the majority of tracking cookies in 2017 and 2018, respectively. Google's move, which could be announced at its developer conference in Mountain View, Calif., starting Tuesday, is expected to be touted as part of the company's commitment to privacy -- a complicated sell, given the torrent of data it continues to store on users -- and press its sizable advantage over online-advertising rivals.

Microsoft is unveiling a number of new features for its upcoming Edge Chromium browser today. From a report: The first big addition is a new "IE Mode" for Edge that will allow businesses to load old sites directly in the new Edge Chromium browser, using the Internet Explorer rendering engine. Microsoft is building IE directly into Edge for this purpose, so businesses aren't forced to directly use IE for ancient internal sites. "What we're going to do is make this totally seamless," explains Microsoft's Joe Belfiore, in an interview with The Verge. Currently, the existing version of Edge will open Internet Explorer 11 on Windows 10, which has a separate interface, favorites, and doesn't work well on modern websites. This new IE mode literally loads the content within Edge, so you'd never be able to tell the difference, apart from a small IE logo on the tab that indicates that this mode has been enabled.

This new IE mode is designed exclusively for businesses, and Belfiore admits it's a big pitch to get them to use Edge Chromium instead of a combination of Chrome and Internet Explorer. "We've got a browser for you that updates regularly that will go on Windows 7 and the Mac that handles things like IT customization of the New Tab page and Microsoft Search, and IE built-in," says Belfiore. Microsoft is also allowing businesses to customize the New Tab page for Edge Chromium. This will involve a custom company logo, the option to load some sites into the top tabs, and integration with Microsoft Search and Office 365.

"When you turn on the setting in your browser that says 'Do Not Track', you probably expect to no longer be tracked on most websites you visit. Right? Well, you would be wrong," explains DuckDuckGo's blog.

Their recent study found "a quarter of people have turned on this setting" -- representing hundreds of millions of web surfers -- and that most of them were unaware that in fact, "no law requires websites to respect your Do Not Track signals, and the vast majority of sites, including most all of the big tech companies, sadly choose to simply ignore them."

Now they've written draft legislation -- "the Do-Not-Track Act of 2019" -- to "serve as a starting point" for legislators to close this loophole. SearchEngineLand reports: If the act picks up steam and passes into law, sites would be required to cease certain user tracking methods, which means less data available to inform marketing and advertising campaigns. The impact could also cascade into platforms that leverage consumer data, possibly making them less effective. For example, one of the advantages of advertising on a platform like Google or Facebook is the ability to target audiences. If a user enables DNT, the ads displayed to them when browsing those websites won't be informed by their external browsing history...

This proposal is quite far from being signed into law, but the technology is already built into Chrome, Firefox, Opera, Edge and Internet Explorer. With the adoption of GDPR just a year behind us and presidential candidate Elizabeth Warren's proposed legislation to regulate "big tech companies" drawing more attention to digital privacy issues in Washington, the Do-Not-Track Act could be a realistic outcome.
DuckDuckGo says they're announcing their draft legislation because "It is extremely rare to have such an exciting legislative opportunity like this, where the hardest work -- coordinated mainstream technical implementation and widespread consumer adoption -- is already done....

"We hope the Do-Not-Track Act of 2019 serves as a useful guide to start thinking seriously about this amazing legislative opportunity."

A former web developer at YouTube has revealed a tale about a clandestine operation to kill Internet Explorer 6 with a banner that went live in July 2009 warning IE6 users that YouTube would be phasing out support for Microsoft's browser -- even though no one at Google had endorsed such a plan. From a report: IE6 of course shipped as the default browser with Windows XP in 2001, six years before Chrome's first release in 2008. Google wouldn't officially drop support for IE6 until March 2010, but a group of renegade web developers at YouTube had already pulled off a campaign that coincided with a serious fall in IE6 usage worldwide, from about 25 percent in mid-2009 to less than 10 percent within a year. The campaign consisted of a web banner displayed to IE6 users on YouTube beginning in July 2009. The banner hadn't been officially endorsed by Google, which had acquired YouTube in 2006 for $1.65bn and by 2009 had begun integrating it into the Google infrastructure.

As former YouTube web developer Chris Zacharias details in a blog, the desire to kill off IE6 was that it had become "the bane of our web development team's existence". "At least one to two weeks every major sprint cycle had to be dedicated to fixing new UI that was breaking in IE6. Despite this pain, we were told we had to continue supporting IE6 because our users might be unable to upgrade or might be working at companies that were locked in," he explains.

Zorro shares a report from CBS News: If you're looking for more "Avengers: Endgame" content to fill the void until you get to see the movie, Google has the perfect Easter egg for you. Open Google, search "Thanos," click the Infinity Gauntlet on the right side -- and watch as half of your search results turn to dust. The gauntlet -- complete with the six Infinity Stones -- will snap its fingers when clicked, just as Thanos did in "Avengers: Infinity War." But this time, instead of eliminating half of the universe's population, Thanos will eliminate half your Google Search results, perfectly balancing the internet. Make sure you turn the sound on.

An anonymous reader shares a report: Michael Leggett is even more annoyed with Gmail than you are. "It's like Lucky Charms got spewed all over the screen," he says to me, as he scrolls through his inbox. It's true. Folders, contacts, Google apps like Docs and Drive -- and at least half a dozen notifications -- all clutter Gmail at any given moment. And of course, there's that massive Gmail logo that sits in the upper left-hand corner of the screen. Just in case you forgot that you just typed "gmail.com" into your browser bar three seconds ago. "Go look at any desktop app and tell me how many have a huge fucking logo in the top left," rants Leggett. "C'mon. It's pure ego, pure bullshit. Drop the logo. Give me a break."

Rather than sit there and stew, Leggett decided to do something about it: He created a free Chrome extension called Simplify, where all the extraneous folders and functions overloading Gmail seem to melt away, leaving you with a calm screen and nothing but your messages. It's understatedly beautiful, and every button just seems like it's in the right place. In fact, it feels a little too good for some random free Chrome extension made by some random developer. Let's just say that Leggett was highly qualified for the job. You see, Leggett was actually the lead designer for Gmail from 2008 to 2012. He also cofounded the since-discontinued Inbox, which attempted to reimagine Gmail for the modern era.

An anonymous reader quotes a report from VentureBeat: Google today launched Chrome 74 for Windows, Mac, Linux, Android, and iOS. The release includes support for a reduced motion media query, private class fields, feature policy improvements, and more developer features. You can update to the latest version now using Chrome's built-in updater or download it directly from google.com/chrome.

Motion sickness in the browser is a real thing. Android provides an accessibility option to reduce motion whenever possible, as shown above in the âoeremove animationsâ setting. Chrome is now taking that a step further so websites can limit motion sickness when viewing parallax scrolling, zooming, and other motion effects. Chrome 74 introduces prefers-reduced-motion (part of Media Queries Level 5) that allows websites to honor when an operating system is set to limit motion effects. This might not seem like a big deal today, but it could be very useful if websites start abusing motion effects. Check out the full changelog for more information on this release.

Firefox's former VP accused Google of sabotaging Firefox -- for example, when Gmail and Google Docs "started to experience selective performance issues and bugs on Firefox" and demo sites "would falsely block Firefox as 'incompatible'... There were dozens of oopses. Hundreds maybe... [W]hen you see a sustained pattern of 'oops' and delays from this organization -- you're being outfoxed."

Now Nightingale's accusations have stirred up some follow-up from technology reporters. An anonymous reader shares a blog post by ZDNet security reporter Catalin Cimpanu: Nightingale is not the first Firefox team member to come forward and make such accusations. In July 2018, Mozilla Program Manager Chris Peterson accused Google of intentionally slowing down YouTube performance on Firefox. He revealed that both Firefox and Edge were superior when loading YouTube content when compared to Chrome, and in order to counteract this performance issue, Google switched to using a JavaScript library for YouTube that they knew wasn't supported by Firefox.

At this point, it's very hard not to believe or take Nightingale's comments seriously. Slowly but surely, Google is becoming the new Microsoft, and Chrome is slowly turning into the new IE, an opinion that more and more users are starting to share. On Twitter, a senior editor at the Verge added "Google did a lot of 'oops' accidents to Windows Phone, too. Same pattern of behavior with its services and Edge. Oopsy this, oopsy that." The site MSPowerUser also shares a similar story from former Microsoft Edge intern, Joshua Bakita. "I very recently worked on the Edge team, and one of the reasons we decided to end EdgeHTML was because Google kept making changes to its sites that broke other browsers, and we couldn't keep up."

Meanwhile, Computerworld argues that data "backs up Nightingale's admission, to a point." [I]f Google monkey business contributed to Firefox's fall, it must have really damaged Microsoft's IE. During the time it took Chrome to replace Firefox as the No. 2 browser, Firefox lost just 9% of its user share, while IE shed 22%. And Chrome's most explosive growth - which began in early 2016 - didn't come at Firefox's expense; instead, it first hollowed out IE, then suppressed any potential enthusiasm for the follow-on Edge.

Chrome didn't reach its current place -- last month capturing nearly 68% of all browser activity -- by raiding Firefox. It did it by destroying IE.

Oops.

The Verge explains what all the commotion is about: AMP stands for "Accelerated Mobile Pages," and you've probably noticed that those pages load super quickly and usually look much simpler than regular webpages. You may have also noticed that the URL at the top of your browser started with "www.google.com/somethingorother" instead of with the webpage you thought you were visiting. Google is trying to fix that by announcing support for something called "Signed Exchanges." What it should mean is that when you click on one of those links, your URL will be the original, correct URL for the story. Cloudflare is joining Google in supporting the standard for customers who use its services.

In order for this thing to work, every step in the chain of technologies involved in loading the AMP format has to support Signed Exchanges, including your browser, the search engine, and the website that published the link. Right now, that means the URL will be fixed only when a Chrome browser loads a Google search link to a published article that has implemented support.
Mozilla'a official position on signed exchanges is they're "harmful," arguing in a 51-page position paper that there's both security and privacy considerations. Pierre Far, a former Google employee, posted on Twitter that the change "breaks many assumptions about how the web works," and that in addition, "Google is acting too quickly. Other browsers and internet stakeholders have well-founded concerns, and the correct mechanism to address them is the standardization process. Google skipped all that. Naughty." Jeffrey Yaskin, from Chrome's web platform team, even acknowledged that criticism with a tweet of his own. "I think it's fair to say we're pushing it. The question is our motives, which I claim is to improve the web rather than to 'all your base' it, but I would say that either way."

Search Engine Land cited both tweets, and shared some concerns of their own. "The compromise we have to consider before getting on board with Signed HTTP Exchanges is whether we're willing to allow a third party to serve up our content without users being able to tell the difference.

"If we, as digital marketers, want to influence the conventions of our future work environment, we'll have to decide if the gains are enough to disrupt long-standing assumptions of how websites are delivered. If so, we'll also have to cede the ability to judge user intent over to Google and swallow the fact that it skipped over the standardization process to implement a process that one of its own created."

tedlistens writes: One of the most common techniques people think can help hide their activity is the use of an "incognito" mode in a browser," writes Michael Grothaus at Fast Company. But "despite what most people assume, incognito modes are primarily built to block traces of your online activity being left on your computer -- not the web. Just because you are using incognito mode, that doesn't mean your ISP and sites like Google, Facebook, and Amazon can't track your activity."

However, there's still a way to brew your own, safer "incognito mode." It's called browser compartmentalization. Grothaus writes: "The technique sees users using two or even three browsers on the same computer. However, instead of switching between browsers at random, users of browser compartmentalization dedicate one browser to one type of internet activity, and another browser to another type of internet activity.
Specifically, the article recommends one browser for sites you need to log into, and another for random web surfing and any web searches. "By splitting up your web activity between two browsers, you'll obtain the utmost privacy and anonymity possible without sacrificing convenience or the ease of use of the websites you need to log in to." It recommends choosing a privacy-focused browser like Brave, Firefox, Apple's Safari, or Microsoft's Edge. "As for Chrome: It's made by Google, whose sole aim is to know everything you do online, so it's probably best to stay away from Chrome if you value your privacy."

The article is part of a series titled "The Privacy Divide," which explores "misconceptions, disparities, and paradoxes that have developed around our privacy and its broader impacts on society."

Google's Chrome browser will get a Reader Mode, similar to the one found in competing browsers like Firefox and the old Microsoft Edge. From a report: The feature is currently under development, but Chrome Canary users can test it starting today. Chrome's Reader Mode will work by stripping pages of most of their useless content, such as ads, comments sections, or animations, and leave a bare-bones version behind, showing only titles, article text, and article images. Work on the feature started in February this year when Google engineers began porting the "simplified view" offered by Chrome on Android to desktop editions. Today is the first day that a fully-functional Reader Mode is active in Chrome's desktop versions -- via Google Chrome Canary distributions. To test Chrome's upcoming Reader Mode, users must first visit the chrome://flags/#enable-reader-mode section in their Chrome Canary version, and enable the Reader Mode option.