Today, a test version of the aggregate view has been introduced on the instance. It's a mix of threadiverse and microblog formats, applying all filters, blacklists, sub filters, languages etc. After selecting *, the links to sub, mod, fav change, and navigation works within the aggregate view....
I really like this #feature but currently it seems really difficult to activate it. Could you maybe turn this * button to a switch to indicate when it's on or off and to make sure it doesn't turn off when switching pages?
Well, I did a little digging, and while parts of the stuff proposed by Google might be tricky, the actual topics portion of the API looks pretty easy to spoof. It seems like there’s really only two things that need to be done. The first is to spoof the feature detection logic to return true for calls to document.featurePolicy.allowsFeature(‘browsing-topics’). The second would be to return randomly selected topics from all available topics from calls to document.browsingTopics() (care might need to be taken to return a consistent set of random topics to a given page, otherwise clever sites might poll the API many times to detect randomness). That really seems to be all there is to the topics API part of this. As for spoofing the rest of the web DRM parts, that’s going to be a lot trickier, but with control of the browser I can’t see how it could be made insurmountable.
RTR#27 Aggregate view, work on federation (kbin.social)
Today, a test version of the aggregate view has been introduced on the instance. It's a mix of threadiverse and microblog formats, applying all filters, blacklists, sub filters, languages etc. After selecting *, the links to sub, mod, fav change, and navigation works within the aggregate view....
Feature comparison - kbin vs Lemmy (kbin.social)
There's a chance that I have forgotten something or missed something....
How To Turn Off Google’s “Privacy Sandbox” Ad Tracking—and Why You Should (www.eff.org)
Google did it again.