This is definitely on the roadmap for JupyterLab, and while and end user capability will not be available in 1.0, many of the pieces will be in place.
The Google drive integration is all but dead, as our friends in mountain view decided to sunset the backend. It could potentially be rewritten to use firebase. However, in building (and still maintaining) that library, we now have a pretty good abstraction, IDrive, which is used by the GitHub integration as well as an irods integration. I've also been toying with ipfs/dat implementations which would make p2p sharing possible. As to war stories: I did a prototype in derbyjs (no idea if that's still a thing). It put the whole state of the frontend into a model, which many users could update. https://github.com/nrbgt/derby-notebook It worked, but will definitely benefit from a stronger, official model. Stay tuned, and chime in with any findings! -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/a0b034a0-97ac-481b-a36a-ebb3610e6b96%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
