And since you won’t be able to modify web pages, it will also mean the end of customization, either for looks (ie. DarkReader, Stylus), conveniance (ie. Tampermonkey) or accessibility.

The community feedback is… interesting to say the least.

  • TeoTwawkiEnglish
    -2•1 year ago

    Lets break the near monopoly they have and give what google wants the finger.

    https://duckduckgo.com/windows

    You know how nearly every browser is now based on chromium? And firefox when its not chromium, and even forefox adopted the extension limitations of chrome? Well I hear Duckduckgo’s new browser something new finally instead of based off an existing browser.

    It doesn’t have extensions yet but those are coming and adblock is baked in.

    Ed: my 1st downvotes of my time on the fediverse. <3 you to folks.

    • @dot20English
      19•1 year ago

      even forefox adopted the extension limitations of chrome?

      This is false. I quote blog.mozilla.org:

      One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.

      Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.

      https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/

      I also quote uBlock Origin’s GitHub page:

      uBO works best on Firefox and is available for desktop and Android versions.

      https://github.com/gorhill/uBlock#installation

      • TeoTwawkiEnglish
        0•1 year ago

        Ty apreciate the correction

        I was more reffering to what we lost compared to the old addon system tho.

        (I don’t understand the downvoting of this reply, I at least understood why my previous one was getting them…)

    • Arthur BesseEnglish
      10•1 year ago

      Well I hear Duckduckgo’s new browser something new finally instead of based off an existing browser

      Where did you hear that? According to wikipedia DuckDuckGo’s browser uses the operating system’s rendering engine on mobile (chromium’s on android, and safari’s on ios), and the mac version also uses webkit (safari’s engine).

      The windows version doesn’t appear to even be open source but I would be surprised if it isn’t also using chromium’s rendering engine.

      • TeoTwawkiEnglish
        1•1 year ago

        On windows, theres been more than one, but they said their knew one is all new code by thier own engineers instead of yet another chromium descendant, and I hope to god thats actually true.

        • Arthur BesseEnglish
          1•1 year ago

          they said their knew one is all new code by thier own engineers

          where did they say that?

          • TeoTwawkiEnglish
            2•1 year ago

            Having trouble finding it now, but this is thier own post over on reddit (4 months old now)

            How is it made? DuckDuckGo for Windows was built from the ground up by DuckDuckGo engineers with privacy, security, and simplicity front of mind. We are not forking Chromium (or anything else) and for web page rendering it calls the underlying operating system rendering API (in this case a Windows WebView2 call that utilizes the Blink rendering engine underneath). While this is the approach we’re taking now, that might change depending on the feedback we get from this round of testing. If there are changes to future versions, we will make that clear.

            If you’ve signed up and are waiting for an invite, we appreciate your patience! We’re letting folks in gradually so that we can implement feedback as we go.

            Love from the DuckDuckGo team 🦆

            I’m actually less confident having read this…Isn’t webview2 exactly what edge and chrome do? I now regret opening my mouth.

    • @[email protected]English
      5•1 year ago

      and even forefox adopted the extension limitations of chrome?

      You mean webextensions or webextensions v3? Because when it appeared they announced they’d support v3 but without the limitation.