this post was submitted on 20 Jul 2025
88 points (98.9% liked)
Firefox
20396 readers
168 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
The root of the issue is this idea that a web browser should be an "everything app" that can basically recreate the functionality of any other app on the system. It's total feature creep, and in addition to privacy issues, creates a barrier-to-entry that makes it very hard for people to create new browsers because of the sheer amount of features they're expected to implement.
Couldn't agree more.