5 ms·

I wasn't thinking of blocking specific function calls so much as that data not being available to the browser at all to send in the first place, providing the a

I wasn't thinking of blocking specific function calls so much as that data not being available to the browser at all to send in the first place, providing the ability to selectively block mouse x,y coordinates tracking, etc before the code on the page was executed. Again, this may not be possible without breaking the web given the structure of the browser and what pages need to render at a low level. Perhaps client-side middleware that only passes user data when an action is performed rather than constantly streaming coordinate and interaction data all the time?

Kalium 8y ago
This is a great idea! It's always a good idea to control carefully what information is available to a system you might not always be able to trust completely. It's especially important to be sure you're not leaking info through a channel you didn't consider, which at times means that an allowlisting approach is preferable to a blocklisting approach. Your heart is in the right place. Keep iterating!