- cross-posted to:
- technology@lemmy.world
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
- technology@lemmy.world
You must log in or register to comment.
Unless 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.
They’re based on Chromium, Not Google’s altered version of it.
deleted by creator
It’s in Chromium, the other browsers have just disabled/patched it out: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/components/privacy_sandbox/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:
https://vivaldi.com/blog/technology/heads-up-googles-going-off-topics-again/
deleted by creator
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.
