Hi @yishn,
I put together a little proof of concept go server called teahouse that runs games through a barely modified copy of your p2p-goban. The code is AGPL'd and currently in a state which could be described as a minimum viable product but could be more accurately described as full of bugs, missing functionality and as having code quality issues.
While setting it up, I was wondering about the difficulty in integrating signalhub and the functionality around this.state.peers into the web branch of Sabaki proper. It seems like getting the basic functionality wouldn't be too bad but handling every action that should be shared might be a nightmare to do all at once. What are your thoughts and future plans for it?
Hi @yishn, I put together a little proof of concept go server called teahouse that runs games through a barely modified copy of your p2p-goban. The code is AGPL'd and currently in a state which could be described as a minimum viable product but could be more accurately described as full of bugs, missing functionality and as having code quality issues.
While setting it up, I was wondering about the difficulty in integrating signalhub and the functionality around
this.state.peers
into the web branch of Sabaki proper. It seems like getting the basic functionality wouldn't be too bad but handling every action that should be shared might be a nightmare to do all at once. What are your thoughts and future plans for it?