Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

What will happen for those that use the iframeAPI and are passing interfaceConfigOverwrite and the deployment get updated?

You're absolutely right for that I am planning to:

Keep backward compatibility by merging interfaceConfigOverwrite into configOverwrite.

Would love to hear your thoughts on this approach

I'm not convinced that this is how it needs to happen.
What will happen with all deployments that are still using interface config file for modifications, after the update their modifications will stop working.

Such disruptive changes should go through the community announcements in the forum and The Call and be coordinated by the team.

Hey @damencho, that’s a fair point, it makes sense that it should go through community discussions and proper coordination.

I’ll close this PR for now and let the team decide the best approach for deprecating interfaceConfig.js in a way that doesn’t disrupt users.

We already have a way to migrate settings in base/config (the reducer).

Basically the usual steps are:

• Move a setting to config
• Deprecate it in interface_config
• Still support reading the old value and internally convert it to the new one
• Eventually delete the deprecated value and accompanying support code

This is how we've migrated tons of settings already.

Note that the last step needs a long long time since we don't want to break deployments.