What’s your use case? This is indeed only used for the recent list and calendar screens, both of which are only available in the Jitsi Meet app’s welcome screen.
SDK users don’t see or use this screen so it’s kinda irrelevant, isn’t it?
If someone wants to deploy their own Jitsi Meet build to the store then they probably want to change this in addition to setting their own default server, at which ppoint adding a flag becomes moot, since you’d need to make code changes anyway…
Well, it’s not change for the sake of change. Having other domains referenced in local storage does cast doubt on our claims that the service is self-contained and does not send data to third parties. We know that reference is benign, but I’d rather not have to prove it to customers.
I don’t have a specific implementation in mind, but wanted to gauge appetite for such a change before investing time on a PR
Assuming it is possible, would you consider a PR which enables the default domain list to be overidden from config.js?