258

Ladybird Browser Gains Cloudflare Support to Challenge the Status Quo (linuxiac.com)

submitted 11 months ago by KarnaSubarna@lemmy.ml to c/opensource@lemmy.ml

76 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Damage@feddit.it 12 points 11 months ago

For now

[-] curbstickle@anarchist.nexus 5 points 11 months ago

So when they do just fork it?

I likely won't touch it anyway, but it is fully open source, so it can be forked easily. With the transition to Swift I suspect there would be plenty of devs who could take things forward if they wanted to.

[-] Damage@feddit.it 5 points 11 months ago

If you look at history, Google did the opposite with Chrome, they forked an open source browser and turned it into the world's most used.
I guess we'll see.

[-] curbstickle@anarchist.nexus 2 points 11 months ago

Thats google though, with the added ability to put it direct into an extremely common OS (Android). With ladybird, you've got an apparent neocon and 3 years currently planned for a GA release (2028). Its future is already pretty uncertain regardless of sponsorship.

[-] ReversalHatchery@beehaw.org 1 points 11 months ago

So when they do just fork it?

say the same for chrome, and think again if you mean it seriously.

[-] curbstickle@anarchist.nexus 3 points 11 months ago

Iridium, cromite, edge, brave, thorium, vivaldi, pale moon....

And this is a drastically simpler browser that would be in swift 6.

[-] ReversalHatchery@beehaw.org -2 points 11 months ago

and what can they do against the manifest v3 migration? they cannot afford to keep maintaining the code for mv2 addons. it is an important topic for efficient content blocking.

its funny you bring up edge as an alternative. brave too has opt-out telemetry and other shenanigans.

[-] curbstickle@anarchist.nexus 4 points 11 months ago

I was answering forking and how realistic it is. You're changing the conversation into specifics around chrome.

As I mentioned, this would be (not is, because its not even at a GA state) drastically simpler to fork, and there are many forks of a substantially more complicated browser already.

[-] ReversalHatchery@beehaw.org -2 points 11 months ago

I was answering forking and how realistic it is. You're changing the conversation into specifics around chrome.

I'm not changing anything. they are powerless. if google decides to change chrome for the worse in a more significant way than UI design, they cannot avoid accepting that change.

[-] curbstickle@anarchist.nexus 1 points 11 months ago

Sure thing bud.

Now back to the actual topic.....

[-] Zerush@lemmy.ml 1 points 11 months ago* (last edited 11 months ago)

Well, there is a lot of panic about the change from Mv2 to Mv3, and also a lot of misinformation. It's correct that Mv3 adblocker are somewhat less effective (independent tests don't show much difference, but in change offer a way better security). Inbuild adblocker won't be affected and in other extensions not related to adblocking, it's irrelevant for the user if it is Mv2 or Mv3. Mv2 will disappear sooner or later, same as Mv1 in 2013. Some Chromium Browsers still support Mv2 extensions some time longer (Vivaldi, Opera, Brave), naturally all FF forks, probably until next year, but Mv2 is dying, yes or yes. Only problem exist for uBO, due to it's specific structure need to be practically remade from scratch to be compatible with Mv3, until now Gorhill only released uBO Lite Mv3, Meanwhile AdGuard and Adblock Plus already are in Mv3

Differences

Recent research and implementation data reveal several key advantages of Chrome's Manifest V3 (MV3) over Manifest V2 (MV2):

Security Improvements

Enhanced extension architecture that limits access to sensitive data[^4]

Disallows remote code execution, requiring all code to be contained within the extension[^5]

Stricter privacy protocols that minimize data collection[^4]

Performance Benefits

Optimized resource management through updated background processes[^4]

More efficient performance through the new declarativeNetRequest API[^2]

Anti-Tracking Capabilities

Recent studies show MV3 ad blockers blocked approximately 1.8 more trackers per website compared to MV2 versions[^6]

Specific improvements in individual tools:

Adblock Plus MV3 blocked 21.5% more trackers than its MV2 version

Stands MV3 showed a 45.9% improvement in tracker blocking[^6]

Enhanced Combined Protection

Using multiple MV3 ad blockers together significantly improved anti-tracking effectiveness compared to single blockers[^6]

No reduction in ad-blocking capabilities compared to MV2, contrary to initial concerns[^6]