By enabling this option, it will be possible to connect to rooms using external XMPP accounts and XMPP clients.<br> <span class="peertube-plugin-livechat-warning"> <b>Warning</b>, enabling this option can request extra server and DNS configuration. </span> Please refer to the documentation: <a href="https://livingston.frama.io/peertube-plugin-livechat/documentation/admin/advanced/xmpp_clients/" target="_blank"> Enable external XMPP account connections. </a>
The port that will be used for XMPP s2s (server to server) connections.<br> You should use the standard 5269 port. Otherwise you should <a href="https://prosody.im/doc/s2s"> setup a specific DNS record </a>.
The network interfaces to listen on for server to server connections.<br> List of IP to listen on, coma separated (spaces will be stripped).<br> You can 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>
There might be some very technical strings. If you are not 100% sure of the meaning, or of your translation, you better not translate it, so it will display in english.
This plugin relies on [ConverseJS](https://conversejs.org/) for the chat front-end.ConverseJS has its own translations, on its own [weblate instance](https://hosted.weblate.org/projects/conversejs/#languages).You can also translate directly in the code repository.For more information, check [ConverseJS translations documentation](https://conversejs.org/docs/html/translations.html).
If this field is empty, the plugin will generate and use self-signed certificates.<br> If you want to use other certificates, just specify here the folder where Prosody can find them. Note: the "peertube" user must have read access to this folder.
If you think there is a missing locale, please check first if it is handled in Peertube.If so, you can [open an issue](https://github.com/JohnXLivingston/peertube-plugin-livechat/issues) to ask for it.