live-share VS instant.nvim

https://github.com/MicrosoftDocs/live-share/issues/3524

Edit: ah it might be about the IP: https://github.com/MicrosoftDocs/live-share/issues/3279

The API is closed and the visual code binaries prohibit reverse engineering. See also https://github.com/MicrosoftDocs/live-share/issues/3299

maybe this https://github.com/jbyuki/instant.nvim.

For example, instant.nvim just shows where other clients are currently inserting. Assuming you don't do something daft like invite 500 strangers for a free-for-all, you shouldn't run into any problems.

You could also force your coworkers to use neovim and everyone can use https://github.com/jbyuki/instant.nvim (/j)

This has already been working in other forms for years, see for example https://github.com/mhinz/neovim-remote which is now more or less discontinued because the respective core implementation is indeed better longterm (again - this is a difference because this implements an unopinionated extension protocol that’s now easy to deliver with the refactoring efforts, not an opinionated packaged solution). A useful and fuller experience for the special case of remote editing would be https://github.com/jbyuki/instant.nvim for example, they also use this API principle you wanted to see - it’s just a nvim-server that is controlled remotely and you have an editor locally that acts as your direct interface (and you take this functionality into every other embedded solution!). And all of that is not just just somewhat fiddled solution but iterated solutions of the varying states of this feature implementation (on the path to neovim 1.0).

This plugin looks promising. https://github.com/jbyuki/instant.nvim

I've been keeping an eye on instant.nvim, though I haven't used it yet