2. PeerTube LiveChat
3. Russe
4. Zen

25 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Bullet: '* ' `reuse`
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/100 · 7 À vérifier
26 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text Please note that this plugin needs an AppImage for the Prosody XMPP server. This AppImage is provided by the [Prosody AppImage](https://github.com/JohnXLivingston/prosody-appimage) sideproject. The `build-prosody.sh` script download binaries attached to this remote repository, and checks that their sha256 hashsum are correct.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/3290 · 329 À vérifier
27 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text Clone the repository, buid the plugin, and create your feature branch:
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/700 · 70 À vérifier
28 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Fenced code block (bash) # Clone the repository. Dont forget the --recursive to clone submodules. git clone https://github.com/JohnXLivingston/peertube-plugin-livechat.git --recursive cd peertube-plugin-livechat # Install NPM dependencies and build the module for the first time: npm install # Build the plugin after a modification: npm run build # If you have a fork from the repository, add it as remote (example): git remote add me git@github.com:MY_GITHUB_ACCOUNT/peertube-plugin-livechat.git # Create a local branch for you developments, and checkout it (example): git checkout my_development # Note: if an issue is associated, use fix_1234 as your branch name (where 1234 is the issue's number) # To propose your modifications, push your branch to your repository (example): git push --set-upstream me my_development # Then go to your github repository with your web browser to propose the Pull Request (see additional instructions below)
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/9250 · 925 À vérifier
29 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text Once you are ready to show your code to ask for feedback, submit a *draft* Pull Request. Once you are ready for a code review before merge, submit a Pull Request. In any case, please link your PR to the issues it solves by using the GitHub syntax: "fixes #issue_number".
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/2720 · 272 À vérifier
30 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text The front-end code is in the `client` folder, the back-end code in `server`. There are some shared code in `shared` folder.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/1230 · 123 À vérifier
31 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text For general instructions (developping plugins, building, installation, ...), please refer to the [Peertube documentation](https://docs.joinpeertube.org/contribute-plugins?id=write-a-plugintheme).
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/1950 · 195 À vérifier
32 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text You can build the plugin with extra debug features simply by using:
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/670 · 67 À vérifier
34 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text This plugin is [REUSE](https://reuse.software/) compliant: it uses SPDX headers to identify licensing information of its source code. More information on the [REUSE](https://reuse.software/) website. You can use the [reuse](https://reuse.readthedocs.io/en/stable/readme.html#) command line tool to help you update headers. The `npm run lint` command will use the `reuse` command to check compliance. Don't forget to add your copyright information in SPDX headers when you modify some code.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/4930 · 493 À vérifier
chat_terms_label
	Anglais Terms & Conditions
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/180 · 18 À vérifier
35 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Title ## ESBuild vs Typescript
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/210 · 21 À vérifier
chat_terms_description
	Anglais These terms & conditions will be shown to all users when then join chatrooms. Streamers can also configure terms & conditions for their channels, that will be shown right after these global terms & conditions.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/2100 · 210 À vérifier
36 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text This plugin uses ESBuild for frontend code generation, as the official `peertube-plugin-quickstart` plugin. ESBuild can handle Typescript, but does not check types (see [ESBuild documentation](https://esbuild.github.io/content-types/#typescript)). That's why we first compile Typescript with the `-noEmit` option, just to check types (`check:client:ts` in package.json file). Then, if everything is okay, we run ESBuild to generate the compiled javascript.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/4590 · 459 À vérifier
37 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Title ## Debug Mode
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/100 · 10 À vérifier
38 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text There is a debug mode for this plugin, that shorten some delay. For example, some log files will rotate every two minutes, instead of once per day. This permit to test more easily certain actions, for which it could normally take hours or days to wait.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/2540 · 254 À vérifier
39 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text To enable this mode, you juste have to create the `/var/www/peertube/storage/plugins/data/peertube-plugin-livechat/debug_mode` file (replacing `/var/www/peertube/storage/` by the correct path on your installation).
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/2140 · 214 À vérifier
40 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text The simple existence of this file is sufficient to trigger the debug mode. To make sure it's taken into account, you can restart your Peertube instance.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/1530 · 153 À vérifier
41 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text This file can contain some JSON to enable more advanced options. To have a list of existing parameters, check `server/lib/debug.ts`. Restart Peertube after each content modification.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/1840 · 184 À vérifier
federation_dont_publish_remotely_description
	Anglais By checking this setting, your instance will not publish chat information on the fediverse. Remote Peertube instances will not be aware that they are chat rooms associated to your videos.<br> <b>Please note</b>: if you already had chats in progress, it is possible that the information has already been published. You will have to wait for the next video update before the information is unpublished. Also, if you disable this setting, you'll have to wait for the videos to be updated before the information are published again. This update happens among others when a live event resumes or stops.<br> <b>Please note</b>: this setting only affects the publication of information via the ActivityPub protocol. It will not prevent a remote application from otherwise detecting the presence of chats, and trying to connect to it.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/8270 · 827 À vérifier
42 support/documentation/content/en/contributing/develop/_index.md
	Anglais type: Plain text Don't enable this mode on a production server, neither on a public server. This could cause security issues.
	Russe ↹ ↵ NBS … « » „ “ ﹙-﹚ ‐ – — 0/1090 · 109 À vérifier