Which interface_config.js options can be overwritten via the API?

ubuntourist · April 20, 2020, 6:27pm

Hi,

We’re hosting our own Jitsi Meet, and it would be nice, when doing screen sharing, to temporarily hide the watermark.

Testing with the example in the API documentation filmStripOnly: true worked as described, but trying SHOW_JITSI_WATERMARK: false did not.

Is there a list of which options can be overwritten and which cannot? Or am I doing it wrong?

TayebBou · July 14, 2020, 5:50pm

this is what i want to know too @damencho could you explain us please ?

damencho · July 14, 2020, 6:08pm

Can be changed on your own deployment. If you are using meet.jit.si you cannot hide the watermark as this is against the terms-and-conditions: http://jitsi.org/meet-jit-si-terms-of-service/

TayebBou · July 14, 2020, 6:09pm

thank you you look cool in your picture

damencho · July 14, 2020, 6:09pm

What is whitelisted you can check here:

github.com

jitsi/jitsi-meet/blob/master/react/features/base/config/configWhitelist.js

import extraConfigWhitelist from './extraConfigWhitelist';

/**
 * The config keys to whitelist, the keys that can be overridden.
 * Currently we can only whitelist the first part of the properties, like
 * 'p2p.useStunTurn' and 'p2p.enabled' we whitelist all p2p options.
 * The whitelist is used only for config.js.
 *
 * @type Array
 */
export default [
    '_desktopSharingSourceDevice',
    '_peerConnStatusOutOfLastNTimeout',
    '_peerConnStatusRtcMuteTimeout',
    'abTesting',
    'analytics.disabled',
    'audioLevelsInterval',
    'autoRecord',
    'autoRecordToken',
    'avgRtpStatsN',

This file has been truncated. show original

github.com

jitsi/jitsi-meet/blob/master/react/features/base/config/interfaceConfigWhitelist.js

/**
 * The interface config keys to whitelist, the keys that can be overridden.
 *
 * @private
 * @type Array
 */
export default [
    'AUDIO_LEVEL_PRIMARY_COLOR',
    'AUDIO_LEVEL_SECONDARY_COLOR',
    'AUTO_PIN_LATEST_SCREEN_SHARE',
    'CLOSE_PAGE_GUEST_HINT',
    'CONNECTION_INDICATOR_AUTO_HIDE_ENABLED',
    'CONNECTION_INDICATOR_AUTO_HIDE_TIMEOUT',
    'CONNECTION_INDICATOR_DISABLED',
    'DEFAULT_BACKGROUND',
    'DISABLE_PRESENCE_STATUS',
    'DISABLE_JOIN_LEAVE_NOTIFICATIONS',
    'DEFAULT_LOCAL_DISPLAY_NAME',
    'DEFAULT_REMOTE_DISPLAY_NAME',
    'DISABLE_DOMINANT_SPEAKER_INDICATOR',

This file has been truncated. show original

TayebBou · July 14, 2020, 6:11pm

amazing this is what i’m looking for thanks

ubuntourist · July 14, 2020, 7:01pm

That is why I started with:

damencho · July 14, 2020, 7:31pm

You can change SHOW_JITSI_WATERMARK in interface_config.js on your deployment.

ubuntourist · July 14, 2020, 7:58pm

Sigh.

That is what I keep trying to tell you I did. Three months ago.

I edited /usr/share/jitsi-meet/interface_config.js
I changed “SHOW_JITSI_WATERMARK: true” to “SHOW_JITSI_WATERMARK: false”.
I saved the file.

I ran:

     systemctl restart jicofo.service
     systemctl restart jitsi-videobridge2.service
     systemctl restart prosody.service

The watermark did not disappear.

But that was three months ago. I’ll try again – when the system is not being used…

damencho · July 14, 2020, 8:00pm

You don’t need to restart anything after doing this change.
Check index.html source whether your change is there.

ubuntourist · July 15, 2020, 1:41am

Nope, (We added a custom CSS and custom footer, but neither references any watermark.) And I refreshed the browser cache, but the watermark stays.

corby · July 18, 2020, 1:47am

@ubuntourist,

Just upload a single pixel transparent image to your server called blank.png and try this technique:

Edit your nginx config: /etc/nginx/sites- available/meet.example.com.conf

Add a block like this:

location /images/watermark.png {
    alias /path/to/my/blank.png;
}