• YurkshireLad@lemmy.ca
    link
    fedilink
    arrow-up
    8
    ·
    18 hours ago

    I immediately blocked the new AI features. It’s cunningly strange how they worded it. “Toggle on to block AI features”, which means some people might look at it and think “it’s turned off, so the AI stuff must be disabled”. Sneaky.

    • Vincent@feddit.nl
      link
      fedilink
      arrow-up
      2
      ·
      2 hours ago

      I imagine that UI was kind of hard to put together though, since it’s going to be confusing anyway. The UI is meant to allow people to toggle everything off, and add exceptions that they want to leave on. The reverse, however, is not needed: people don’t really want to toggle everything “on”, and then selectively disable things. To top that off, you also want to clarify that, after you toggle things off, new AI features that get added later will also be off automatically.

      I imagine especially that latter part influence the “toggle on to block” design - that makes it an “active” setting to proactively disable things in the future.

      IDK, I’m not a UI designer, but I see how it’s hard.

    • MyTurtleSwimsUpsideDown@fedia.io
      link
      fedilink
      arrow-up
      6
      ·
      15 hours ago

      I ran into a skeezy GDRP prompt the other day that was turn on to opt out. I thought it was weird that the default was “off” then I found the little greyed out opted-in to sharing data text under the option titles which changed to green opted out when I turned the toggle on.

      But at least Mozilla is clear and direct about how the toggle works. Heck, they even put a big ol’ billboard on the ‘what’s new in this release’ page showing you how to do it with a link directly to the setting.