this post was submitted on 11 Aug 2024
399 points (100.0% liked)

Technology

37737 readers
425 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

uBlock Origin will soon stop functioning in Chrome as Google transitions to new browser extension rules.

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@beehaw.org 10 points 3 months ago* (last edited 3 months ago)

Its still the same extension, same source code, same logic, just less capable

the same… but not the same… ??

I think the technologies are quite different.

uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing -- uBOL's service worker process is required only when you interact with the popup panel or the option pages.

Are you claiming non-lite does the same, plus more?

You say it's the same source code, but it's a different source code repository. non-lite, lite.