Usecase: I have my stream player on the curated website community.xyz , which plays back a given stream ID from LP. I want this player to be open to different communities to contribute at different times, but I don't want to give them the Stream Key. Instead, I would like them to have unique keys to a stream router which then uses the main Stream Key. This way I can create a truly decentrally curated AV publication.

You can add watch party feature same as Amazon Prime Video watch party where people can watch together and if someone pauses it get paused for everyone and if someone moves it forward or backward it does for everyone. And everybody has control over video, but we can add additional feature like we can restrict the control to selected people. My name is Yash. I really loved your concept. I am Crypto tech enthusiast from 2012 and would love to contribute to blockchain technology.

Currently, the tutorial for engagement analytics ( https://docs.livepeer.org/developers/guides/get-engagement-analytics-via-api ) only focuses on retrieving VoD analytics. Users have a hard time understanding what to do about live streams, both during the stream and after the stream. In addition, users have a hard time understanding the difference between "Query viewership metrics", "Query usage metrics", "Query public total views metrics", and "Query creator viewership metrics" in the API reference because there are no descriptions on how to use those endpoints.

This improvement to Playback Policies will further secure private streams, and prevent users from sharing signed urls to unauthorized viewers

RE: Asset deleter at https://docs.livepeer.org/api-reference/asset/delete Feedback 1: it could be made more clear that the required string to be passed into 'Authorization' field is 'Bearer <ownerAPI>' Feedback2: It would be great to input arrays of Asset IDs instead of one by one.

As a streamer, I want to be able to start my stream before "going live". This can help me gain confidence in my setup. This can be implemented in the application by hiding the stream from users until the user clicks on "go live". But currently, if recording is on, the footage of the stream prior to "going live" is also recorded. This can be solve by allowing a non-recorded stream to start recording in the middle of the stream. Note, it probably doesn't make sense to stop recording in the middle of a stream.

It's easier to download an OBS config file than having to read the "Stream via OBS" guide ( https://docs.livepeer.org/guides/developing/stream-via-obs ) and change every configuration.

It is difficult to find a specific session in the dashboard for debugging purposes. We should map and revamp this user journey (inc. filtering, etc)

Right now, the webhook UI does not allow retrys, browsing of history, etc. We should revisit this UI to ensure that it is suited to the needs of scaled applications

I want to provide free access to the first 10-15 seconds of a video, then cut access if needed