rgadellaa’s avatarrgadellaa’s Twitter Archive—№ 9,523

  1. …in reply to @yatil
    @yatil As far as I know, FLoC was announced as a standard while it was still in development (not when it was already implemented, so they could get feedback), launched as an experiment (for more feedback), then canceled because of feedback.
    On twitter.com Twitter logo rgadellaa’s avatar Mood +1 🙂
    1. …in reply to @RGadellaa
      @yatil To counter; Apple's ITP is proprietary, was announced as "this is it, incredible", not very open to feedback (just deal with it, we're protecting privacy) and broke sites - then turned out to actually do the opposite of what it was supposed to do.
      Permalink On twitter.com Twitter logo rgadellaa’s avatar Mood -1 🙁
      1. …in reply to @RGadellaa
        @yatil And WebKit browsers on iOS actually have some of ITP forced onto them, no way to disable it when it turned out it was basically a huge fingerprint, no extra work required.
        Permalink On twitter.com Twitter logo rgadellaa’s avatar Mood -2 🙁
        1. …in reply to @RGadellaa
          @yatil Also not convinced Google would make it a requirement for their web services. They could make 3rd party cookies a requirement and force Brave, Vivaldi, etc, to not block them? That said, I guess I can't prove what Google may or may not do at some point in the future so 🤷
          Permalink On twitter.com Twitter logo rgadellaa’s avatar Mood +2 🙂
          1. …in reply to @RGadellaa
            @yatil I will absolutely admit that Google is very keen on being able to keep its ad business, but there's actually another side to the FLoC story: Chrome wanted to block 3rd party cookies but wasn't allowed by regulators (because then only Google could track users through Chrome)
            Permalink On twitter.com Twitter logo rgadellaa’s avatar Mood -1 🙁