Re: [w3c/gamepad] Please don't restrict to a secure context (#145)

Apologies if I'm poking a stale issue here, however, I wanted to add my 2 cents to this discussion.

I maintain a piece of controller emulation software that allows users to send webpage-based gamepad input to a Nintendo Switch. Users mainly host this webpage locally and connect to it on the same network. The recent move to restrict gamepad use to a secure context has left me in a bit of a bind. I'm being forced to consider two options with this change: 1) Coaching users through accepting a self-signed certificate or 2) Dropping gamepad input from the project altogether. Both options further complicate use of the software for users.

I realize that I'm a bit too late to affect any real change on this topic, however, I would at least like to state, for the record, that this move is negatively affecting the project that I maintain.

Additionally, if the overall goal for the future is to move the entire platform to a secure context, where does this leave small/casual projects on local networks? Is the recommended path going to be coaching users through self-signed certificate warnings? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/145#issuecomment-925482171