▲ 1403 ▼ Google gets its way, bakes a user-tracking ad platform directly into Chrome (arstechnica.com) submitted 3 years ago by teft@startrek.website to c/technology@lemmy.world 356 comments fedilink hide all child comments
[+] mind@lemmy.world 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Spotlight7573@lemmy.world 3 points 3 years ago (1 child) 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/ permalink fedilink source parent hideshow 2 child comments replies: [+] mind@lemmy.world 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Spotlight7573@lemmy.world 2 points 3 years 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. permalink fedilink source parent
[–] Spotlight7573@lemmy.world 3 points 3 years ago (1 child) 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/ permalink fedilink source parent hideshow 2 child comments replies: [+] mind@lemmy.world 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Spotlight7573@lemmy.world 2 points 3 years 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. permalink fedilink source parent
[+] mind@lemmy.world 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Spotlight7573@lemmy.world 2 points 3 years 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. permalink fedilink source parent
[–] Spotlight7573@lemmy.world 2 points 3 years 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. permalink fedilink source parent