• Treczoks@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    The only issue with this otherwise great idea is that “the developer says, that…”. A browser API should have a way to only grant certain rights when this is technically disclosed, e.g. an extension can only access location data if this is (formally) declared, and must be able to cope without it if the user or any global policy disallows it.

  • pHr34kY@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    This is a great change. I wonder how long before the hate brigade comes along to complain.

    • Zagorath@aussie.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      Yup, sounds great to me. I could see a world in which it becomes a bad thing because they try to enforce it by pulling a Google and blocking users from installing extensions that aren’t through their official add-on store, but as it is, it’s hard to see any reasonable criticism.

  • This2ShallPass@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    It is possible that any developer could just say “none” even if the extension does collect data? If it has to be manually disclosed, this won’t stop malicious actors. Only trustworthy extension developers would disclose this.

    • Bobo The Great@startrek.website
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      Since some extensions are “mozilla-approved”, I guess they test it regularly, it wouldn’t be hard to verify if one is really sending anything despite their disclosure.