At the time of writing this article, the following is the output: We can look at the current version from the DevTools by pressing Ctrl+ Shift+ I, then going to the “Console” tab, and finally typing erAgent in the console. In this example, I’m using Discord Canary from flathub-beta ( ). We can set 'DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING': true in ~/.config/discord/settings.json ( ~/.var/app//config/discord/settings.json for Flatpak) or use Discord Canary. The stable client blocks us from accessing the DevTools by default.

Let’s first look at what Electron version Discord is based on, because it’s going to come in handy for the rest of the article. In this article, we’re going to look at PipeWire and Wayland compatibility, specifically the lack thereof and the potential security risk with their practices. The Discord client uses an Electron version that is questionably low. However, Electron has one major drawback: it is up to the application developer to update (rebase) to a newer version of Electron to fix security bugs, improve stability and improve compatibility with newer technologies. Electron facilitates deploying the same application in different desktop platforms. Thanks to Electron, the framework that Discord uses, it was possible for Discord to port the client over to Linux very easily. Introductionĭiscord is popular among the Linux desktop community. Some of the issues listed below have been addressed and annotated. AnnouncementĪt the time of updating this article, Discord updated to Electron 22.3.2, which is based on Chromium 1.215. I also haven’t contacted the Discord developers, so information may be wrong. Determining the Electron Version in Useĭisclaimer: This post is not meant to attack the Discord developers, rather to write in hope that Discord will listen to the Linux community about practical issues with the Discord client on the Linux desktop.A Letter to Discord for not Supporting the Linux Desktop

Discord canary