Ryan Bliss
Ryan Bliss
**Describe your user scenario** If a developer wants to use our `RoleVerifier` or `SharedClock`, they must first use `joinContainer`. If a developer wants to use Live Share DDS for a...
**Describe your user scenario** User becomes frustrated when they draw a stroke that was incorrectly placed. **Describe the solution you'd like** Undo/redo latest stroke, eraser, line, clear action, etc. Anything...
### Please review [FAQ and Known issues](https://github.com/microsoft/live-share-sdk/issues/8) before filing a new item! - [X] I have reviewed the FAQ and known issues and did not find my topic **Describe your...
Fluid V2 is now in beta, so for Live Share v2 we need to support it as it includes breaking changes.
There are lots of issues with strict dependency settings in Live Share, since we use child packages of the `fluid-framework` package in Live Share. With non-strict settings (default for npm...
Currently `LivePresence` relies on having received updates from each client for determining offline/online. But audience is more reliable and gets these changes faster. We plan to integrate presence with audience.
With Live Share V2, we plan to remove the "preview" label from live-share-react and support it officially.
We plan to remove the live-share-turbo package, having found the experimental concepts to be successful. New plan is to integrate the concepts into the core live-share package.
We have found that the `ILiveShareHost` `registerClientId()` function is not actually necessary. Because `userId` is included in the Fluid token, we can safely have each client get the Teams `userId`...
**Describe your user scenario** For large meetings / connection volume, it is important to have a small amount of clients that can send outgoing signals when possible. so that developers...