Google has just released Chrome 90 to the stable channel. There aren't too many UI changes or new features for us regular folks on the surface, but under the hood, Google has added a whole slew of improvements that you'll certainly notice over time. You'll get enhancements to copy-and-paste, better AR models, and support for a new codec that uses less bandwidth during video conferences.
After years of propping up widespread adoption of the protocol, Google will release Chrome 90 as the first version of the web browser to transmit data to and from sites using HTTPS instead of HTTP by default.
Chrome has finally reached the 80s. The browser sadly doesn't have a neon theme or play The Power of Love at startup, but maybe Google is saving that for v85. Regardless, this version has plenty of changes to go into, so let's dive in.
After a short rollout delay, Chrome 79 is now widely available on desktop and mobile platforms. That means Chrome 80 has moved up to the beta channel, and while there are a few new features, there are far more removed features. Let's dive right in!
HTTPS has largely replaced its less secure predecessor HTTP as the default choice for sending resources over the internet. The key difference between the two is that HTTPS transmits data using an encrypted connection, while data loaded over HTTP is not. Google began marking all sites still utilizing HTTP connections as 'Not Secure' with the release of Chrome 68 last year, and today, Google announced additional plans to inform users when sites utilize an insecure connection. With these latest changes, the Chrome team hopes to address the problem of mixed content.
Earlier this year, the team behind Chrome stated that all HTTP pages will be marked as 'Not secure' later on this year, in a bid to encourage even more site owners to move to the more secure HTTPS standard. We now know a little bit more about planned changes to Chrome's security indicators, including how HTTPS pages will be shown as default pages going forward.
Three years ago, Google paid $25 million for exclusive rights to the '.app' top-level web domain. At long last, the company is now opening up registrations for .app, with the Early Access Program in full swing. The general public will have to wait until May 8, but various companies have already bought over 3,000 .app domains.
The whole web is slowly marching towards HTTPS, especially since browsers like Chrome are starting to shame HTTP-only sites. After years of readers asking why we haven't already done so, I'm proud to announce that Android Police now supports HTTPS! If you're wondering what exactly that is, or why it matters, read on.
For years, HTTPS was regarded as only necessary for sites handling critical information, like bank portals. The movement for all sites to use HTTPS has gained traction over the past few years, partially thanks to the availability of free SSL/TLS certificates from Let's Encrypt, and partially thanks to browsers encouraging sites to switch. Starting with version 68, Chrome will start marking all HTTP sites as 'Not Secure.'