Chrome not proceeding with Web Integrity API deemed by many to be DRM
9to5google.com
Back in July, Google's work on a Web Integrity API emerged and many equated it to DRM. The company announced today it's not proceeding...

While WEI is thankfully cancelled, it’s not entirely cancelled… They’re planning on making it available still in WebViews with the intention that websites can check if a malicious Android app is trying to do a phishing scheme.

Seems like such a niche “security” feature… what are they really trying to accomplish here? Something seems fishy to me

    • 4dpuzzle@beehaw.orgEnglish
      10·
      1 year ago

      A win is when we have forced them to abandon the wretched plan. Them taking it elsewhere with a different name, only to be brought back in the future isn’t a win - it’s more or less the folly the Trojans committed with the Greek wooden horse.

        • 4dpuzzle@beehaw.orgEnglish
          2·
          1 year ago

          I don’t trust Google’s word that they will keep it that way. Besides, would you have accepted this proposal if WEI wasn’t proposed first? It’s a form of manipulation.

          • Big P@feddit.ukEnglish
            1·
            1 year ago

            Sites inside webviews can already communicate with the app running them, I don’t see how this proposal in this form causes any additional problems

            • 4dpuzzle@beehaw.orgEnglish
              1·
              1 year ago

              The same can be said about WEI on browsers. Just wait till it becomes a problem - only problem is that you won’t be able to escape it at that point.

              • Big P@feddit.ukEnglish
                1·
                1 year ago

                Except websites can’t just communicate directly with the OS like they can in webviews

      • java@beehaw.org
        9·
        1 year ago

        We have won the battle, but the war is not over. If one is tired, he or she could employ escapism. But don’t blame or poke those, who don’t do that.