91
submitted 6 days ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 26 points 6 days ago

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.

[-] [email protected] 5 points 6 days ago

It's not direct hardware access. It is pretty restricted in what it can do compared to Vulkan, for example, and what you can is checked by either the shader compiler or the api implementation itself at runtime to make sure the program is not doing something nefarious.

load more comments (8 replies)
this post was submitted on 20 Jul 2025
91 points (98.9% liked)

Firefox

20428 readers
10 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.


Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner


Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.


founded 5 years ago
MODERATORS