• Noah@lemmy.federated.club
    link
    fedilink
    English
    arrow-up
    44
    ·
    edit-2
    1 year ago

    Luckily, other browser manufacturers (Mozilla, Vivaldi, Brave, and even the WWWC) have already spoken out against this proposal. Google loves marketing it as ‘optional’, which it obviously won’t be once implemented. A system like this would be very dangerous for smaller browsers, as it’s incredibly vague who decides what authorities would be allowed to verify browsers.

    Additionally, this is presented as a way to remove captchas from the web by proving a request is coming from genuine hardware. However, this proves absolutely nothing about a request being genuine or non-spam. The only thing this proves is that it was created by a ‘genuine device’, so all a malicious user would have to do is to (automatically) send the request via a verified device and they’d pass the check.

    • sgtlighttree@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Maybe it’s just Google search (ironic), but I couldn’t find anything about the W3C speaking against the proposal. If W3C is against it then I think it’s even more likely the entire thing would be shot down.

      • Noah@lemmy.federated.club
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Could’ve sworn I saw it in an article or post on here somewhere… but of course now that I actually need the post I can’t find it. Doesn’t really matter though, Chrome can unfortunately push standards through even if others don’t approve, just due to their sheer size alone.