v0.6.0

Yapmod v0.6.0 introduces community themes and the first version of the community plugin system, making it possible to customize Yapmod beyond what the desktop application provides out of the box. It also marks a major cleanup of the injected client, a new Solid.js-based architecture, and a separation of stable and nightly client updates to make releases easier to maintain.

Highlights

• Community themes. Community themes are now supported through the Community Themes section. You can create your own themes and publish them for others to discover and use. The Yapmod website includes documentation explaining how to create a theme and submit it to the community collection.
• Community plugins. The plugin system is now officially available, allowing developers to extend Yapmod using a dedicated plugin API. Community plugins can be published through a process similar to community themes. The system is still experimental, and the API documentation is currently minimal. Both the API and its documentation will continue to evolve as the system matures.
• Custom Background plugin. The first community plugin is already available: Custom Background. It lets you customize the application's background with an image of your choice and change the accent color. This plugin was developed to make extensive use of the new plugin API and serves as an initial example of what developers can build with it.

Improvements and fixes

• Client architecture and maintainability. The injected client has undergone a major internal refactor. Previously, much of the interface was built using native DOM manipulation and manually constructed strings. The client now uses Solid.js to handle UI components and DOM updates in a more structured way. This simplifies UI development and makes the codebase easier to maintain.
• CSS separation and client cleanup. Styles that were previously embedded in JavaScript files have been moved into dedicated CSS files. The broader cleanup also removes unnecessary complexity and improves the structure of the client, laying the groundwork for more reliable future development.
• macOS interface improvements. Several adjustments have been made to improve the interface on macOS, continuing the work on making Yapmod feel more integrated with the platform.

Development and infrastructure

• Separate stable and nightly client updates. Stable and nightly releases now have independent client update channels, following an approach similar to Discord's stable and Canary clients. Previously, publishing a stable client update could depend on changes that were only available in the nightly development branch. Separating the two channels removes this dependency and allows each to evolve independently.
• Stable channel. The main branch is now dedicated to stability, security fixes, hotfixes, and maintenance. It will not receive new experimental features as part of the normal development process. This keeps stable releases focused on reliability.
• Nightly channel. The nightly branch is dedicated to ongoing development and new features. Automated builds are published daily, giving users and developers access to the latest changes before they reach the stable channel. Nightly builds may be unstable and are intended for testing.
• Experimental plugin ecosystem. The plugin infrastructure is now in place, including an API designed specifically for plugin development and a community distribution process. However, the system is still experimental. Expect further improvements to the API, additional documentation, and changes as development continues.

Nightly v0.5.1+nightly.20261030.14

Automated nightly prerelease built from the nightly branch at commit 79e7d0c.

App version: 0.5.1+nightly.20261030.14

Nightly builds may be unstable. They use the nightly update channel and never publish stable artifacts or stable client update metadata.

v0.5.0

yapmod v0.5.0

Yapmod v0.5.0 adds support for separately versioned client updates and fixes a Windows startup issue that could keep Yapmod's settings interface from loading correctly. It also improves titlebar controls, settings navigation, theme startup, and topbar notifications.

Highlights

• Independent client updates. Yapmod now supports client bundles published separately from desktop app releases. When a compatible update is available, it verifies the signed manifest and bundle hash, checks app compatibility, and stages the update. Yapmod then offers a restart to apply it; active calls will disconnect, and an update that fails to start is rolled back.
• Windows settings and titlebar. Fixed a Windows startup issue that could keep Yapmod's settings interface from loading correctly. Client startup now waits for the document root and head before installing its observers and styles, so the settings interface can integrate with Yapper's page. Windows also gets minimize, maximize or restore, and close controls in Yapper's top bar. Follow-up fixes restore button clicks and authorize the window commands. On macOS, the host top bar serves as the window drag area.
• Topbar notifications. Compact notification banners now appear in Yapper's top bar.

Improvements and fixes

• Theme initialization waits until the document root exists, and injected styles wait until the page head is available. This makes startup styling more reliable.
• Fixed settings navigation freezes caused by repeated event listeners and a mutation observer loop. Added icons to Yapmod's settings sections.
• Updated Yapmod's Yapper integration for yapin.gg, including the supported bare and www addresses used to open the app and load the injected client.

Development and infrastructure

• Daily and manually triggered nightly builds are now published as rolling prereleases for testing. Nightly builds may be unstable and do not have the stability guarantees of a stable release. They embed the client built from the same source revision.
• Moved the injected client into its own client/ directory and added versioned, signed client release tooling. The embedded client in this release is version 1.0.2; client and desktop app versions remain separate and compatible versions are still required.
• Unified the project checks, shared the app build workflow between stable and nightly packages, and improved portable and Windows MSI version handling. Removed unused Vite scaffolding and updated the website and desktop guides, including the AppImage limitation on some Wayland systems.

v0.4.1

yapmod v0.4.1

Fixed

• Theme mode changes now update the active styles without reloading the page.

v0.4.0

yapmod v0.4.0

This release introduces system tray support and built-in theme support!

New

• System tray support: yapmod keeps running in the background when its window is closed, so desktop notifications continue while the window is hidden. This works on macOS, Windows, and most Linux desktop environments with tray indicators.

• Theme support: Load custom themes directly into yapmod from dedicated folders containing a CSS file and a manifest.json file. The format and requirements are documented in the project documentation.

Install

Download the build for your platform below.

macOS builds are ad-hoc signed but not notarized. The first time you open yapmod, right-click the application and select Open to launch it.

v0.3.1

yapmod v0.3.1

This release makes the desktop notifications and the unread badge actually work.

Fixed

• Desktop notifications now show up. The webview cannot post notifications by itself, so yapmod hands them over to the system. Yapper still decides when to notify you: muted channels and servers, Do Not Disturb and a window that is in front are all respected.
• The unread count reaches your app icon. The number of unread messages now shows on the Dock, on the taskbar and on the panel, where the system supports it.

New

• Two options in Settings → Yapper → Yapmod: Desktop notifications and Show the unread badge. Both are on by default.
• Clicking a notification brings yapmod to the front and opens the message it was about.

Install

Download the build for your platform below. macOS builds are ad-hoc signed but not notarized, so right-click yapmod and choose Open the first time.

v0.3.0

yapmod v0.3.0

This release is about the things you use every day: notifications, voice calls, and keeping yapmod up to date.

What's new

• Notifications and mentions. Unread counts and mention badges now show up on servers and channels, and yapmod can show desktop notifications and play notification sounds. This works on Windows, macOS and Linux.
• Voice calls on macOS. macOS now asks for microphone access the first time you join a call. Allow it and your microphone works.
• Update notices. yapmod checks for new versions and tells you when one is available. You can turn the automatic check off in settings.
• Changelog in settings. Read the notes for every yapmod release without leaving the app.
• A documentation site. Setup, first-launch, troubleshooting, FAQ and developer docs now live on the website, with full-text search.

Fixed

• Switching settings sections no longer leaves the previous panel visible.
• Settings from older yapmod versions now carry over correctly.
• The Linux app uses the proper Tux icon.

If your microphone still does not work

Open System Settings → Privacy & Security → Microphone, enable yapmod, and relaunch. If yapmod is not listed, run this in Terminal and relaunch:

tccutil reset Microphone io.ilyeshdz.yapmod

Install

Download the build for your platform below. macOS builds are ad-hoc signed but not notarized, so right-click yapmod and choose Open the first time.

v0.2.0

Settings, links, and a website

This release puts yapmod's options where you expect them: inside Yapper's own settings page. It also adds an official website with direct downloads and makes external links open in your normal browser.

Highlights

• Added a Yapmod section to Yapper's settings, so desktop options live next to the rest of the app.
• Added an official landing page with direct download links for macOS, Windows, and Linux.
• External links now open in your default browser instead of inside the app.

New

• The native titlebar and start-maximized options can now be toggled from the settings page, and apply on the next launch.
• Settings are stored in your config file and can be written to from the injected page.
• The release notes modal now shows the version, release date, and changelog of every past release.

Fixed

• Following a link to another site no longer opens a broken window inside the desktop client.

v0.1.2

Changes

• The app now opens the sign-in screen when you are not logged in, instead of the website landing page.
• macOS builds are properly signed, fixing the "The app is damaged and can't be opened" error.

macOS note

This build is ad-hoc signed but not notarized. On first launch, right-click yapmod.app and choose Open, or allow it in System Settings → Privacy & Security.

Install

• Windows: .msi installer or NSIS .exe
• macOS: .dmg (Intel and Apple Silicon)
• Linux: .deb, .rpm, or .AppImage

v0.1.1

Changes

• Fixed macOS builds reporting "The app is damaged and can't be opened" by properly signing the app bundle.

macOS note

This build is ad-hoc signed but not notarized. On first launch, right-click yapmod.app and choose Open, or allow it in System Settings → Privacy & Security.

Install

• Windows: .msi installer or NSIS .exe
• macOS: .dmg (Intel and Apple Silicon)
• Linux: .deb, .rpm, or .AppImage