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

Ill also mention I use gamepad for robotics controller, like many in this thread. We often work with government agency's where our platform is **_NEVER_** allowed to access the real internet. We host our own internal LAN and everything is completely isolated.

Luckily, we use an electron app as our controller, which localhost is considered a secure context, but we have projects planned where we don't want a user installed app and instead them just go to a website. 

Can install a fake SSL certificate using something like `mkcert` but then the user has to accept the self signed certificate and browsers love to tell the user they are doing something scary by not being on HTTPS. It's just an added complication for projects where this added security is pointless and leads to more things to go wrong from the users perspective. 

I think the requirement for HTTPS is pushed solely by large corporations that have it all figured out, but it really fucks up the development process and the ability for small creators to make things.

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

Message ID: <w3c/gamepad/issues/145/1933044298@github.com>