[deleted]
Comment on Google gets its way, bakes a user-tracking ad platform directly into Chrome
csolisr@communities.azkware.net 1 year agoUnless the developers of other browsers take specific steps, the ad engine will get pulled on the next update of their Chromium engine, that’s the problem.
mind@lemmy.world 1 year ago
Spotlight7573@lemmy.world 1 year ago
It’s in Chromium, the other browsers have just disabled/patched it out: …googlesource.com/…/privacy_sandbox_prefs.h
// Un-synced boolean pref indicating if Topics API is enabled.
inline constexpr char kPrivacySandboxM1TopicsEnabled[] = “privacy_sandbox.m1.topics_enabled”;`
e.g. Vivaldi:
mind@lemmy.world 1 year ago
[deleted]Spotlight7573@lemmy.world 1 year ago
They have forked it though? That’s why almost all the other Chromium-based ones don’t have this enabled by default or completely disable it (even if you tried to turn it on).
If you’re talking about forking the entire project and using it as a base that diverges from what Google does, I don’t think that’s going to happen. Not even Microsoft with their billions had the desire to maintain a totally separate engine anymore and I don’t see the other Chromium-based browsers redirecting efforts from useful things like better UIs, privacy enhancements, etc into just keeping feature/performance parity.
account_93@lemm.ee 1 year ago
They’re based on Chromium, Not Google’s altered version of it.
csolisr@communities.azkware.net 1 year ago
Yeah, about that…