Goodbye FLoC, hello Topics

There are an awful lot of extensions that rely on content page JS injection, so I think it's more likely they'd adjust the Chrome Store policies to disallow hooking browsingTopics() (including whatever automated extension testing they have). The end result is effectively the same - any such extension could only be side-loaded, which is fine for technical folks, but as good as non-existent for regular users.