- From: Jim (JR) <notifications@github.com>
- Date: Thu, 13 Jan 2022 09:27:47 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 13 January 2022 17:27:59 UTC
@AshleyScirra But what if the context is ***NOT*** "localhost"? What if the browser is on a different system? Many of the use-cases I envision are remote devices like a robot and are going to have a given hostname depending on the situation it is used in. @pyalot The problem is that, especially with hardware devices, secure connections are not always feasible. This is why I suggested a hardware access option similar to what is already used for access to the microphone or camera. As I said: >Conclusion 1: Placing stuff behind a secure context is ***NOT always the answer*** Conclusion 2: Placing stuff behind a secure context should ***NOT be the first-choice, knee-jerk reaction*** to a potential security/privacy issue. Conclusion 3: The W3C group ***should exhaust all other possibilities*** before placing a feature - especially a hardware feature - behind a security paywall. I just hope they listen. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/4#issuecomment-1012350786 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/4/1012350786@github.com>
Received on Thursday, 13 January 2022 17:27:59 UTC