Yeah, a lot of these fingerprinting capabilities seem like things that should be behind permission requests, if not outright disabled entirely.
Like ok, I get that if someone wanted to make a browser-based audio editing tool, it might be useful for javascript to be able to sample the output side after effects have been applied. But I don’t want every single fucking website to have that capability by default. I’m not even sure I want websites to be able to play audio at all without permission.
By default, it should be a one way pipeline. Whatever they put into the pipeline gets displayed or played but they can’t see any of the system-specific results. I’d prefer the standard be designing pages to work with any resolution instead of letting them query the exact pixel dimensions, which varies per device and I suspect fingerprinting was the reason they were designed like that in the first place.
Yeah, a lot of these fingerprinting capabilities seem like things that should be behind permission requests, if not outright disabled entirely.
Like ok, I get that if someone wanted to make a browser-based audio editing tool, it might be useful for javascript to be able to sample the output side after effects have been applied. But I don’t want every single fucking website to have that capability by default. I’m not even sure I want websites to be able to play audio at all without permission.
By default, it should be a one way pipeline. Whatever they put into the pipeline gets displayed or played but they can’t see any of the system-specific results. I’d prefer the standard be designing pages to work with any resolution instead of letting them query the exact pixel dimensions, which varies per device and I suspect fingerprinting was the reason they were designed like that in the first place.