Next feature I'm advocating for is something like requestFullscreen but for iframes to become the main window and take over the URL bar.
-
-
Replying to @cramforce @wycats
One thing I'd love to hear ideas for: can we allow running arbitrary JS in a way that doesn't allow fingerprinting?
4 replies 0 retweets 2 likes -
-
Right. Pre-rendering can only be done if the publisher cannot know that it is happening. Fingerprinting is one side channel to know.
1 reply 0 retweets 0 likes -
To be clear: it is ok for the pub to know that pre-rendering happens. Just not that it happens to you.
1 reply 0 retweets 0 likes -
Replying to @cramforce @wycats
so, the fingerprinting would occur when the page is pre-rendered for display by search?
2 replies 0 retweets 0 likes -
ah. i see. the page is pre-rendered when my search results are displayed and the page runs some js that tells the publisher about it.
1 reply 0 retweets 0 likes -
so they learn that i searched for a term that they are indexed for, but not what my search was?
1 reply 0 retweets 0 likes -
Imagine you search for diarrhea, FooMD gets pre-rendered and you click Wikipedia. Now you go to
$site and see re-targeting ads for diarrhea2 replies 0 retweets 0 likes -
Replying to @cramforce @lawnsea
I think it would be acceptable to explore a path that didn't allow the HTML page to run any JS, and restricted it to a worker.
2 replies 0 retweets 1 like
Or deferred JS until the page was rendered for real.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.