jonwchu
jonwchu on Hacker News
Since we are only sharing what is necessary for the collaboration, this is significantly lighter-weight compared to screen sharing. Addressing latency is absolutely a core principle of our design.
Hey there! We have been thinking through multiple headless scenarios. Thanks for the feedback!
I'm curious to hear what you think of collaborative debugging that we also demonstrated with Live Share?
Yes, the data goes over an Azure relay, but we are investigating using a peer-to-peer communication for sharing as well.
We don't transfer all keyboard and mouse inputs. Instead, we communicate the data behind each collaboration activity (e.g. opening and editing source files, initiating debug sessions, stepping through code, etc.). We only transfer what is needed during the collaboration session.
We authenticate when people try to use the link. We are exploring ideas on how to enable fine-grain permissions for sharing.
The link is an association between team members who are in a live share session. The workspace (i.e. source files) is not stored in the cloud. During a live share session, the communication is facilitated by an Azure Relay in the cloud. We are also looking at the ability to have peer-to-peer communication if you are on the same network.
Hey there! Another PM on Visual Studio Live Share here. Security is absolutely something we are designing for. Microsoft will not be collecting data on the code. The code is not stored or uploaded in the cloud in any way. Rather, it is just a connection that is established between you and the teammate you are sharing with.
There's more details in the FAQ here: https://code.visualstudio.com/docs/supporting/live-share-faq