if they outright forced us to stop day one there’d be outrage, so they instead ease us in. first a popup, then a timed popup, slowly leading to their actual goal but without the risk of an initial outrage. i know this is an extreme comparison but we’re like lambs to a slaughter

    • Sha'ul@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      And how much power does Google have to force that on websites that reject it and users who use Lbrewolf or IceCat?

      • ᗪIᐯEᖇGEᑎTᕼᗩᖇᗰOᑎIᑕᔕ
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        All the power that an advertisement network can buy. Especially youtube since it’s owned by google. And advertisers will be happy to have a way of forcing site visitors to run ads/malware or else they will not get served the content.
        It’s similar to certain bank apps refusing to function on Android devices with an unlocked bootloader: you want the convenience of an e-banking application (/ad-driven corporate website)? – Your device (/web browser) “security” must be verified by the “authority” who actually owns your operating system, else you won’t. Everyone* will “be loving” their secure devices, because they “just work”.

        *who is a potential customer buyer and therefore relevant

        Google is trying to use their dominance to actually own the www. The comment/issue section of the github site of the proposal is quite enlightening, if you have the time … especially their reactions on the general dismissal and condemnation of the proposal as unethical.

        • Sha'ul@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I do not use the native YouTube website. I do not have a Google/Gmail account. I do not use chromium, Chrome, or Edge, or Brave. I disable webscrpts and manually temporarily enable them as needed with all webscripts disabled again after Ivclose the browser. I don’t use nathive Android or iPhone. I have all 3rd party scripts and cookies blocked by default.

          I never interact with any Google tracking or Google service on any of my electronic devices. I do not use Google search. Whatever happens with Google I will not see since I do not access anything Google on a monthly basis.

      • probablyaCat@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Well if your bank website and the websites to pay your bills only work with their drm, then ff, ice weasel, etc just won’t work on those sites if they don’t include it. And tech like that, oh big business would fucking love.

        • Sha'ul@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          I use IceCat with NoScript, PolicyBlock, DecentralEyes to block 3rd party, and some other add-ons to access bank and pay bills.

          • probablyaCat@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Yes and that works currently. But recently Google put a proposal in the chromium engine that could essentially function total webpage drm. If that proposal goes through, and websites such as your bank and electricity company start requiring that feature in order to login, then other browsers would be completely locked out. Changing user agents wouldn’t work, because it is a client side check requested server side. Google argues that it would give websites a way to verify they are interacting with a human and limit abuse. That we wouldn’t need captchas and such. That it would increase security. But it could also mean you are totally locked out using alt browsers.

            There is already a similar thing done on ios with safari. But ios doesn’t have a monopoly on users and obviously businesses like your bank or your electric company won’t decide to lock out anyone from paying except with an iPhone. But if Chrome did it, and ios already does it… boom.

            • Sha'ul@lemmy.ca
              link
              fedilink
              arrow-up
              0
              ·
              1 year ago

              While I do not outright dismiss your argument, I believe this general discussion is getting amplified or heightened by people who are neither programmers nor hackers. For the record, hackers are typically good people, it’s the crackers that cause the problems.

              I have faith too many people who are I.T. engineers would strongly resist for Google to have a complete stranglehold on the entire internet. The more people are hurdled into a single way of thinking, the more diverse the resistance becomes.

              I’m not going to be concerned until the intermet has a collective whole says Librewolf doesn’t work for websites, ungoogled chromium doesn’t work for websites, and Brave browser doesn’t work for websites. Less than that, I will dismiss it as sensational drama.

              • probablyaCat@kbin.social
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                I’m not trying to form an argument. I’m trying to tell you they are already doing it.

                Here is the wiki description. Here is the commit adding it after they got massive backlash from the community and in spite of it. Instead, the person who made the commit made a blog whining that people are mean and they don’t have any better ideas. Then they made a code of conduct for those that wanted to comment. Here is even an explanation from google for the WEI. Some good quotes

                It can

                Detect non-human traffic in advertising to improve user experience and access to web content

                The proposal calls for at least the following information in the signed attestation:
                The attester’s identity, for example, “Google Play”.
                A verdict saying whether the attester considers the device trustworthy.

                Providing a signal that is unique to the attester could be hazardous if websites decide to only support attesters where certain signals are available. If websites know exactly what browser is running, some may deny service to web browsers that they disfavor for any reason. Both of these go against the principles we aspire to for the open web.