Announcement

Collapse
No announcement yet.

Chrome 72 Has Some Wayland Improvements, Eyes Deprecating FTP

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Chrome 72 Has Some Wayland Improvements, Eyes Deprecating FTP

    Phoronix: Chrome 72 Has Some Wayland Improvements, Eyes Deprecating FTP

    In addition to Mozilla releasing Firefox 65, the release calendars also aligned today with Google introducing the Chrome 72 web browser...

    http://www.phoronix.com/scan.php?pag...rome-72-Stable

  • #2
    They should deprecate USB/PS2 mouse input.

    Comment


    • #3
      Google are bloody nazis... there's going to come a point in time where their software is unusable for me and I'll have to go back to Firefox. They don't get to dictate how the Internet is going to be.

      I already hate that it redirects URLs to https. Why do I want that overhead on all sites? When I read sites (I don't mean editing or submitting anything) I don't want https, moreover, if I'm connected through a VPN it fails the HSTS check on a lot of sites. So I have to type "badidea" or "thisisunsafe" (changed out from under foot in Chrome 65+, thanks for that) just to read a wikipedia article.

      I don't use Chrome (or Chromium, which is too onerous to build these days), but Vivaldi that uses chrome at the back end. Soon Google's arrogance will affect me too.

      Deprecating ftp links... go boil your bum. There are still a lot of downloads that use ftp for the actual file transfer. Ever download drivers from a manufacturer's web site?

      They are also talking about crippling the ability of extensions to modify network requests (think filtering extensions), disingenuously claiming that it's for "our" protection and performance. This, on the heels of Microsoft adopting it for their dumbed down Edge browser. We can't have users being able to control network requests...

      Comment


      • #4
        Originally posted by Grogan View Post
        I already hate that it redirects URLs to https. Why do I want that overhead on all sites? When I read sites (I don't mean editing or submitting anything) I don't want https, moreover, if I'm connected through a VPN it fails the HSTS check on a lot of sites. So I have to type "badidea" or "thisisunsafe" (changed out from under foot in Chrome 65+, thanks for that) just to read a wikipedia article.
        What? Forced HTTPS redirection? That will greatly hurt me since I can't use a certificate because I don't have a true domain...

        Comment


        • #5
          Not forced in that manner, if https isn't enabled on a site it will connect with normal http.

          I don't do certificates for my sites (just self signed) so if someone explicitly connected with https it would go to the certificate warning but http is http.

          Comment


          • #6
            Let's deprecate every protocol in the name of security.
            I got a better idea. Let's deprecate the whole browser.
            That way we can stop with the madness of having a bit more security if you pay for that and in only case for limited amount of time.
            Or jump through hoops and get a certificate for a even shorter period of time.

            Comment


            • #7
              Ftp is a horrible protocol that needs to die. Hopefully this will entice whatever remaining ftp-only sites there are to update to http(s). (And while they're at it, add rsync as well.)

              If not, we'll, there's always lftp. Or curl.

              Comment


              • #8
                Originally posted by Danny3 View Post
                Let's deprecate every protocol in the name of security.
                I got a better idea. Let's deprecate the whole browser.
                That way we can stop with the madness of having a bit more security if you pay for that and in only case for limited amount of time.
                Or jump through hoops and get a certificate for a even shorter period of time.
                Yeah, but that's the reason Google is developing the browser, not to make the web better but to drive it to where they want, just like Microsoft, except that the latter lost the browser wars.

                Comment


                • #9
                  They should deprecate Google Chrome

                  Comment


                  • #10
                    Mozilla's management is borderline nuts, Opera's compression is effectively neutered because everyone's gone https (and uses a Chrome engine variant backend) and Google's evil. Film at eleven.

                    Comment

                    Working...
                    X