| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Note
2026/06/01 I no longer use this plugin, and do not have a very effective way to validate/test changes. As such, this repo is being archived. I would encourage you to check the StreamController-Store for a forked/updated version.
Note
Only the official Discord application is currently supported. Alternate clients may not work, and unfortunately I don't have the capacity to troubleshoot at the moment.
Warning
Vesktop will not work with this plugin. This is an issue with Vesktop, and not something I can fix in this plugin.
If you are using the Flatpak version of Discord, Discord may not properly setup the IPC channels. You will need to use the commands below to create the IPC channel to communicate with Discord.
mkdir -p ~/.config/user-tmpfiles.d
echo 'L %t/discord-ipc-0 - - - - app/com.discordapp.Discord/discord-ipc-0' > ~/.config/user-tmpfiles.d/discord-rpc.conf
systemctl --user enable --now systemd-tmpfiles-setup.serviceYou will also need to make sure that Discord has access to /run/user/1000/ to be able to create the IPC file.
Configurable by allowing access to xdg-run/discord:create.

If you are using the Flatpak version of StreamController, you will need to make sure StreamController has
access to /run/user/1000/discord-ipc-0 so it can access the IPC files. You can achieve this by adding xdg-run/discord-ipc-0 to Flatseal.

This plugin uses sockets to communicate with Discord. Discord creates this socket as $XDG_RUNTIME_DIR/discord-ipc-0. To verify that only process is listening to this socket, perform the following:
| Back | FazBrowse Home | New Git URL |