Exposed Keys

[om3n07]

There are two exposed keys in the backend folder:
https://github.com/ByronHsu/Never-Blink/blob/master/backend/server.key
https://github.com/ByronHsu/Never-Blink/blob/master/backend/server.key.org

[ByronHsu]

Hi @om3n07 !
I have trouble in setting socket-flask to https. After searching lots of related topics on it, I use flask-sslify to solve it but it still cause the following problems.

1. It will raise error when client connects, but the server still works fine.
2. Developers needs to generate their own key to set up the https server. It is a little bit troublesome.
   Did you have solutions to these problems? Thanks!

[no-1ne]

Get rid of backend, using TF.js for blink detection do it client side, and for webrtc signalling there is firebase or equivalents

[conradkirschner]

Blink detection in the client side will enable cheating, you should never handle win conditions on clientside!

this whole thing is pretty pretty nice, it's 2 years old and maybe not maintained anymore... but still nice + great idea!