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

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    7
    ·
    3 months ago

    Its still the same extension, same source code, same logic, just less capable; hence the addition of “Lite” to the name. Originally they wanted release the Lite version with same name, but changed it Lite, so people don’t get confused why its not longer blocking everything it blocked before.

    • ivn@jlai.lu
      link
      fedilink
      English
      arrow-up
      13
      ·
      edit-2
      3 months ago

      I don’t think it’s the same source code (uBOL vs uBO). And it’s definitely not the same logic, that’s the whole point, blocking with MV3 must be done in a declarative way.

    • Baggins [he/him]@lemmy.ca
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 months ago

      The developer specifically released the light version because they acknowledged that it is not the same and you need to make the explicit choice of what you want to keep using

    • Kissaki@beehaw.org
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      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.