related to #68, it moving to forced https, it might be nice to have a way for users to generate a share link that will populate their entire state from a different location (or in this case, in the new https site). In the absence of login and a true backend, this will also give people the ability to access their "account" from another machine.
I can see a few problems with this though - someone could inadvertently (or intentionally, which would be not cool) use this feature to replace someone else's entire state. So there would have to be a clear warning what's about to happen if one of these share links was popped into the browser.
Maybe the better solution is just to add a true backend and passport login to the site. But still - how to handle existing progress? Maybe just a launch a whole new site.... and tell people on the surge site that its deprecated and to come on over? Could add a redirect, but people would lose all their progress... ugghhh. I dunno...
related to #68, it moving to forced https, it might be nice to have a way for users to generate a share link that will populate their entire state from a different location (or in this case, in the new https site). In the absence of login and a true backend, this will also give people the ability to access their "account" from another machine.
I can see a few problems with this though - someone could inadvertently (or intentionally, which would be not cool) use this feature to replace someone else's entire state. So there would have to be a clear warning what's about to happen if one of these share links was popped into the browser.
Maybe the better solution is just to add a true backend and passport login to the site. But still - how to handle existing progress? Maybe just a launch a whole new site.... and tell people on the surge site that its deprecated and to come on over? Could add a redirect, but people would lose all their progress... ugghhh. I dunno...