brave-browser: Unable to view https://wooorm.com/server-components-mdx-demo/ due to fingerprinting

To show an example with the famous enwik8

$ npx bin2png /tmp/enwik8 /tmp/enwik8.png 
npx: installed 2 in 2.379s
Converting /tmp/enwik8 to /tmp/enwik8.png
Success. File size difference: -11%

And comparing the base64 png to the base64 raw text, the ratio is even slightly better. Of course the ratio highly depends on how compressible the source data is.

1. encode your JS (or arbitrary data) as a base64 data url
2. include that in a script tag
3. mark the tag async

The PNG is not only decoded asynchronously, it is also a compressed data representation that is decompressed asynchronously.

(Im closing the issue now, but lets keep discussing here if it’d be helpful)

cc @lovasoa too, that might work 🤔

And also good to know that the canvas is the problem, not the url!

hi hi! So, was wondering, could you do the following:

1. encode your JS (or arbitrary data) as a base64 data url
2. include that in a script tag
3. mark the tag async

Would that cover the use case here?

(and as background for folks who find this later, Brave doesn’t modify data uri’s, we modify the results of canvas readback, which in this case is being encoded as a data uri 😃 )