This message was deleted.

One approach is to send these over data channels and catch it via room events to update the UI for other participants, if you want to update a db as well you can catch it via webhoohs. HTH

I understand it's desirable for your application to control participant metadata from the client, but because others rely on this security model, it's not a simple feature that can be added. Long term, we do plan to make this more flexible so clients have much more capabilities around managing shared data. In the mean time, it seems fairly straight forward to implement it by calling your own backend API. It does add a bit of latency, but it's negligible.

I agree with @dry-elephant-14928. You can have your own backend & implement this type features. We're also developing conferencing system where we're using seperate backend server to process requests. Later sending changing metadata using backend server directly. After that client can get response on metadata update.

Thanks @dry-elephant-14928 it will surely help maybe in future where we have flags which allows such different behaviours.