We have some functionality for defining in-browser server routes, etc. but that's still pretty nascent... basically, describe an OpenAPI of your routes, and it just kinda... works. Anyhow, in the near term, having a release of jupyterlab-videochat that could fall back on a UUID if public room creation failed would meet the need, and make for a really nice demo.
Over on https://github.com/jtpio/jupyterlite/pull/58 i've gotten videochat at least drawing on the page in a jupyter-serverless environment.
We have some functionality for defining in-browser server routes, etc. but that's still pretty nascent... basically, describe an OpenAPI of your routes, and it just kinda... works. Anyhow, in the near term, having a release of
jupyterlab-videochat
that could fall back on a UUID if public room creation failed would meet the need, and make for a really nice demo.