I’m a webmaster that refuses to use third-party assets, cookies, and tracking of any kind. When Instagram got caught inserting JavaScript in its webviews I added HTML to shoot it down. When FLoC was introduced I added HTTP headers effectively disabling it on my websites.

Does the new Topics API have a similar solution for us web developers? I’d hate to simply block the entire Chrome User-Agent because I know many of my visitors are using Chrome.

  • railsdev@programming.devOP
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I realistically can’t block Chrome users unfortunately. It’s a small business so it’s nothing super fancy.

    Looks a lot like the FLoC stuff, easy enough to add. Thanks!