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

Technology

37730 readers
758 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
[–] [email protected] 96 points 3 months ago (7 children)

More people should use Firefox. Anyone who does not want Google to control the web browser space with a single base. Firefox will continue support uBlock Origin in its full strength. Notice, Google does not "kill" uBlock Origin, but rather weaken it substantially with a new protocol.

But I get it. With such headlines more people will read it. At least it has a good effect of getting attention of people, who would otherwise ignore it.

[–] [email protected] 36 points 3 months ago (6 children)

They do kill uBlock Origin. The Lite version is a different extension.

[–] [email protected] 7 points 3 months ago (5 children)

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.

[–] [email protected] 14 points 3 months ago* (last edited 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.

load more comments (4 replies)
load more comments (4 replies)
load more comments (4 replies)