Hacker News new | past | comments | ask | show | jobs | submit login

It's one thing to prompt the user when you start recording and another to need to go to chrome://flags.

Permissions for privacy invading features should IMO have a unified interface like they have in the OS like Mountain Lion.




The need to go to chrome://flags has nothing to do with privacy.


You need to go to chrome://flags to enable Web Audio Input. The request for the microphone has nothing to do with that .. it's working with or without Web Audio Input.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: