Choose how you want to navigate the web with Firefox | The Mozilla Blog
blog.mozilla.org
As Mozilla envisions Firefox’s future, we are focused on building a browser that empowers you to choose your own path and gives you the freedom to explor

Tldr: Theyre adding an opt-in alt text generation for blind people and an opt-in ai chat sidebar where you can choose the model used (includes self-hosted ones)

  • barryamelton@lemmy.ml
    12·
    4 days ago

    If it was truly opt-in, it could be an extension. They should not be bundling this with the browser, bloating it more in the process.

    The extension API doesn’t have enough access for this.

    You technically can run your own local AI, but they hook up to the big data-hungry ones out of the box.

    While it is opt-in and disabled by default, this is the real problem.

    • LWD@lemm.ee
      3·
      3 days ago

      What are they missing? So far, all they’ve added is a sidebar and a couple extra right-click menu additions. Both of these are available for all extensions.

    • xad@lemmy.ml
      24·
      3 days ago

      The extension APl doesn’t have enough access for this.

      If that’s the case, then it’s pretty great that Mozilla is also the exact company in charge of the extension API.

      I have only one extension, and I use it longer than I use Firefox. I also trust the developer a lot more than I trust Mozilla.

        • xad@lemmy.ml
          1·
          2 days ago

          Mozilla isn’t in charge of the extension API, it uses Chromium’s WebExtensions API

          No. They are basing their implementation on that of Chrome, but nobody is forcing Mozilla to do this … So yes, Mozilla is responsible for all the APIs they integrate. Of course.

          • xor@lemmy.blahaj.zoneEnglish
            1·
            2 days ago

            Yeah, just create an entirely new, incompatible extension engine from scratch for this one feature specifically!

            • xad@lemmy.ml
              1·
              2 days ago

              Yeah, just create an entirely new, incompatible extension engine from scratch for this one feature specifically!

              This is absolutely not how any of this works.

              While Mozilla implements the WebExtensions API based on the W3C standard, they are not bound to a 100% verbatim implementation. Like other browser vendors, Mozilla has the flexibility to extend or modify the API as needed, as long as they maintain compatibility with the core standard. Adding new APIs or features to the extension system does not require creating an entirely incompatible engine. Browser vendors often add non-standard extensions to APIs, which can later be proposed for inclusion in the next version of the standard if they prove useful. So, Mozilla can certainly add new APIs to their extension system without making it incompatible with the existing WebExtensions ecosystem. This is not difficult to understand.