The network interfaces to listen on for external components connections.<br> List of IP to listen on, coma separated (spaces will be stripped).<br> Youcan use «*» to listen on all IPv4 interfaces, and «::» for all IPv6.<br> Examples: <ul> <li>*, ::</li> <li>*</li> <li>127.0.0.1, ::1</li> <li>172.18.0.42</li> </ul>
The external components to declare: <ul> <li>One per line.</li> <li>Use the format «component_name:component_secret» (spaces will be trimmed).</li> <li>Youcan add comments: everything after the # character will be stripped off, and empty lines ignored.</li> <li>The name canonly contain latin alphanumeric characters and dots.</li> <li> If the name contains only alphanumeric characters, it will be suffixed withthe XMPP domain. For example, «bridge» will become «bridge.your_domain.tld». Youcan also specify a full domain name, but you have to make sure to configure your DNS correctly. </li> <li>Only use alphanumeric characters in the secret passphrase (use at least 15 characters).</li> </ul>
<h3>Channel advanced configuration</h3> Following settings concern the advanced channel options: users will be able to add some customization on their channels, activate the moderation bot, ...
In theory, theonly parts of the backend code where you need localization isthe settings declaration and standardized data (ActivityPub, RSS, ...).Here we need to get english strings from the translation key.