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.
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.
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.
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.
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.
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.