David Brochart

The [logic to handle new streams](https://github.com/jupyterlab/jupyterlab/blob/0bd367e40639658d4d1dc29ed41b3d5cb64a3a9b/packages/outputarea/src/model.ts#L508) is not very efficient, as it processes every character and does potentially quite a lot of string concatenations. Again, I think we could defer...

Tests are passing, let me know what you think @krassowski and @fcollonval.

Thanks for the review @krassowski, I tried to take your review into account in https://github.com/jupyterlab/jupyterlab/pull/16498/commits/24cc98d28ab653e41d202e41ede484ecda124387.

Thanks @krassowski, I rebased on `main` and tried to add you as a co-author, but couldn't find your email address.

There is no need to add plugins to this repository, all you need is to create a package which has the following in its `pyproject.toml`: ```toml [project.entry-points] "asphalt.components" = {my_package...

Jupyverse will start all components that are registered in the `"jupyverse.components"` entry point, that's why you need to have this in your `pyproject.toml`: ```toml [project.entry-points] "asphalt.components" = {my_package = "my_package.main:MyComponent"}...

The entry points should be defined in the `pyproject.toml` of the plugin.

This also happens with [jupyter-server](https://github.com/jupyter-server/jupyter_server). It's caused by the `RTC:` prefix added by jupyter-collaboration. There are a number of efforts that will allow to get rid of this: - https://github.com/jupyterlab/jupyterlab/pull/16744...

Hi, I saw that this is in "pending user input", but I guess you are not waiting for anything on my side, right?

Ah, I'm afraid their isn't much yet. I had started https://github.com/davidbrochart/jupyspace, which could be renamed to **multiverse**. Basically the goal is to have something similar to [JupyterHub](https://github.com/jupyterhub/jupyterhub) (multi-user server for...