domschiener / peered Goto Github PK

Make it possible for users to find new games through peers instead of the server.

Do browser check before loading game - suggest better browser if possible and abort process if Browser not compatible with WebRTC.

Under a game, make it possible for players to chat with each other.

When a player disconnects or reloads the browser, make a 5minute reconnect time. Display this message in both in games section (my current games) and in the current game screen for the opponent.

Right now we are rendering the TicTacToe game through data from the server. should we switch to purely client side through the local collection? I have certain problems with that (mostly about consistency).

If creator of game, delete game from the database. If game is currently ongoing, do not quit.

If a user is randomly trying to connect to a peer without joining the game, break up the connection.

Currently peerjs is limited to one game per window, as a new window would request a new PeerID, which is against the current design of Peered. Therefore we need to come up with a solution so that people can play multiple games.

The only way I can imagine this work right now is if the PeerJS object is stored in localstore and continuously accessed when opening new browser windows. This obviously needs to be researches about its weaknesses. Anyone has some ideas?

One of the problems I can see happen is people connecting to peers and sending them invalid play moves. Of course we do a lot of sanity checks on play moves, but I think it would perhaps be smart to implement PKI for signed messages. This way the two players playing against each other know the exact origin of the play moves.

What do you guys think?