This message was deleted.
# helpdesks
steep-balloon-41261
04/15/2023, 8:43 PMThis message was deleted.
d
dry-elephant-14928
04/15/2023, 10:21 PMHey, there isn't a way to limit from livekits side. However you can enforce this within your application in publish options.
f
fierce-winter-46182
04/16/2023, 7:03 AMMy application is going to be open-source, the problem here is that people would then be able to use a higher bitrate and suck my Cloud traffic empty. It would be good to have an option to prevent this, is there maybe some webhook I could listen for that tells me the bitrate of their screenshares or cameras?
d
dry-elephant-14928
04/17/2023, 5:12 AMAre you saying that a user should be free to modify your client code, but at the same time be able to use your keys to connect to LiveKit Cloud?
That doesn't sound like a good idea. TBH
dry-elephant-14928
04/17/2023, 5:13 AMTo answer your question, we are not able to surface bitrate of other clients in real time. This is because it purely depends on what the webrtc client decides to do since bitrate is dynamic in webrtc.
dry-elephant-14928
04/17/2023, 5:13 AMi.e. it's perfect valid for a client to start sending 200kbps.. but then to boost bitrate to 4mbps.. there is no way for us to prevent that.
f
fierce-winter-46182
04/17/2023, 6:04 AMAlright, I didnt know it was that complicated, sorry for asking for something almost impossible. For your question, my Frontend in Flutter is open source while the backend is closed source. I use this approach to be a lot more transparent about what really goes on in the Frontend, so people know what the app they're using does, so there is no security risk there.
👍 1
d
dry-elephant-14928
04/17/2023, 6:07 AMGot it, thanks for clarifying. I'm always paranoid about api key/secret leaking to clients 😅
8 Views