In some rare cases, google sends a 302 found instead of a 206 which can leak a user's IP address as the browser follows the redirect.

I have found a solution, for it but I'm not sure if it would work with #116.

The issue got back some time ago, maybe a week or two. When the page with video gets loaded first time the request to yotter domain occurs but response of that request is 302 redirect to googlevideo domain. uMatrix blocks that requests to googlevideo and so the video doesn't start. You can clearly see the issue in browser's dev console.