Re:Microsoft begins turning off uBlock Origin and other exte...
by Zak on Friday February 28, 2025 @06:47AM
(#43204603)
A quick look at the code gives me the impression that webRequestBlocking is a fairly trivial modification to webRequest, and they seem to be keeping the latter. This leads me to two conclusions: it wouldn't be terribly hard for a fork maintainer to keep webRequestBlocking, and Google's technical excuses for removing it are disingenuous.
Re:Microsoft begins turning off uBlock Origin and other exte...
by justinclift on Friday February 28, 2025 @07:28AM
(#43204877)
> ... and Google's technical excuses for removing it are disingenuous.
That's been the default assumption of pretty much everyone anyway.
Re:Microsoft begins turning off uBlock Origin and other exte...
by account42 on Monday March 03, 2025 @05:28AM
(#43240359)
That may be true now but will it still be true when Google next refactors their request code under the assumption that no requirements for a webRequestBlocking API exist.
Re:Microsoft begins turning off uBlock Origin and other exte...
by SirMaster on Friday February 28, 2025 @05:09PM
(#43212207)
So go make an LLM manage the fork or something. Everyone keeps telling me they are amazing at code these days. Surely it can do a task like that if that's all it's doing all day.
If not today maybe soon...
And that's a lot of work for a multi million LOC project, unless the architecture is specifically made to support such extensions... which isn't the case here.
And freezing your merges indefinitely isn't really viable either for a browser