A recent Youtube Web update has added a canvas whenever the seek bar is visible, an HTML5 canvas pops up. This was not asked for and not needed. If you disable canvases for privacy, this will cause a horrific red bad to cover half the screen until you hide the seekbar. Canvases can be used for fingerprinting, which I’m sure Google is doing here.

  • KairosEnglish
    291·
    4 months ago

    Google uselessly uses the canvas for its reverse image search. And I do mean uselessly - The image you upload is put onto the canvas, then immediately relayed to the server and never used again.

      • KairosEnglish
        68·
        4 months ago

        Yes because as we all know that’s too hard for Google to achieve.

          • KairosEnglish
            16·
            4 months ago

            Yes because as we all know 100% of browsers have a canvas.

              • KairosEnglish
                17·
                4 months ago

                LibreWolf

                TinEye seems to have no problem with this. It seems weird to argue that something that doesn’t work on every browser should be used because the alternative doesn’t work on every browser.

                Google could easily do both. Using JS if canvas fails.

                • lime!@feddit.nuEnglish
                  13·
                  4 months ago

                  librewolf has canvas turned off, because it’s fingerprintable. it’s still in the firefox codebase. all major browsers support canvas and have for more than 10 fifteen years.

                  also, canvas is literally a JS API what are you talking about

        • purplemonkeymad@programming.devEnglish
          2·
          4 months ago

          It’s probably more of a scale thing, going a conversation server side need CPU time, if it can be done prior to upload then server time is reduced. I think a lot of websites do client side processing so they can do more requests per server instance.

        • kevincox@lemmy.mlEnglish
          1·
          4 months ago

          It would be wasteful to upload the full size image only to throw most of it away. JPEG compression is very cheap, especially at low resolutions (I assume that image search uses a pretty low-resolution source image). Doing it this way is actually what I would do for best user experience. (Not saying that they aren’t doing other malicious things, but doing the resizing on the client is actually a good idea)