435
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Oct 2023
435 points (98.9% liked)
Technology
59205 readers
2637 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
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 todocument.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.