I’m not really knowledgeable enough to say for sure, but this sounds like a privacy nightmare. It’s hard enough to keep browsers in general from giving up enough info to identify you even without cookies, but I can’t even begin to see how to stop this from leaking just about everything.
Direct HW access for browsers? Not a fan. What we need is a layer between the browser and the HW that anonymizes and generalizes the API responses instead. I get the increased latency would be directly opposed to what this is trying to achieve, but it’s a prize I’m willing to pay. It’s contrary to what every tech giant wants, which is an indication it’s actually a good idea. They aren’t our friends.
I wonder why a permission-based approach wouldn’t be feasible. Most websites don’t need GPU access anyway, so why couldn’t a game or simulation just prompt the user quickly for granting access to the GPU?
I’m not really knowledgeable enough to say for sure, but this sounds like a privacy nightmare. It’s hard enough to keep browsers in general from giving up enough info to identify you even without cookies, but I can’t even begin to see how to stop this from leaking just about everything.
Direct HW access for browsers? Not a fan. What we need is a layer between the browser and the HW that anonymizes and generalizes the API responses instead. I get the increased latency would be directly opposed to what this is trying to achieve, but it’s a prize I’m willing to pay. It’s contrary to what every tech giant wants, which is an indication it’s actually a good idea. They aren’t our friends.
I wonder why a permission-based approach wouldn’t be feasible. Most websites don’t need GPU access anyway, so why couldn’t a game or simulation just prompt the user quickly for granting access to the GPU?
I wouldn’t even know what the implications of allowing it would be, and I’m a programmer. I just want to play the game.
In other words, the permission prompt would achieve nothing except annoy me and make me ignore prompts.