Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multibrowser synchronized state #82

Open
teisenbe opened this issue Jun 9, 2018 · 3 comments
Open

Support multibrowser synchronized state #82

teisenbe opened this issue Jun 9, 2018 · 3 comments

Comments

@teisenbe
Copy link

teisenbe commented Jun 9, 2018

My friends and I have been playing for a bit, but one of us moved out of town. We wanted to still be able to play, so we've been trying to make it easier to share the game state over the internet. We found your webapp and really liked the idea, but sharing it with screen-sharing wasn't quite as good of an experience as we would like.

We looked into adding support for synchronizing the state based off of the existing localStorage support, but ran into issues. The code architecture didn't lend itself to the asynchronous nature of server-side state management. It was difficult to fix this without rather invasive changes, since a lot of the data flows needed to be inverted. If you're interested in taking a look at our changes, please take a look at https://github.com/drakedevel/gloomycompanion/tree/modernize. We'd be happy to work with you to merge the changes upstream.

Thank you for putting this app together, it's been invaluable for our play!

@teisenbe
Copy link
Author

teisenbe commented Jun 9, 2018

We're of course interested in continuing to contribute and help maintain this code, since it's essential to how we play with our friend.

@GinoGalotti
Copy link
Collaborator

Wow, that's amazing work! Although, it seems that your solution requires users to download and build the solution by themselves (which I assume 99% of the users prefer to just use the online app). We don't do any development on the tool anymore, but now that I'm working with JS again, I don't mind to help if you guys are planning to bring the change.

@teisenbe
Copy link
Author

teisenbe commented Sep 7, 2018

Yeah, it currently requires more work to stand up than your version. One thing we'd like to do is explore how we could provide a hosted version of it. The big thing blocking that is figuring out how to either let folks specify their own storage (Firebase doesn't support this very easily) or make things a little less abusable so no one misuses the Firebase store. We haven't spent too much time looking into that yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants