A few days ago, the Pidgin's development team announced, through an announcement, the availability of the fifth experimental version of Pidgin 3.0, technically labeled as version 2.94.0. This launch is a fundamental step in the long process of renewing this instant messaging client, whose ultimate goal is to completely modernize its architecture and user interface.
Although the developers insist that This is a pre-alpha version not suitable for daily use due to a lack of features Despite the completeness and the presence of errors, this release offers a clear window into the future of the application, with builds already available in Flatpak format through the Flathub beta repository to facilitate testing in secure environments.
Main new features of Pidgin 3.0 Experimental 5
An one of the most anticipated and visible additions in this version is the initial implementation of a functional presence selector. For a long time, this feature had been a missing piece in the 3.0 development branch, but now the uUsers can manage basic states, such as setting oneself as "Away" in protocols like IRC. Although the functionality is operational and correctly reflected in the demo protocol, the team admits that there is still work to be done, including creating a dedicated editor to customize these states and ensure their full persistence across sessions.
In terms of visuals, significant improvements have been made in accessibility and aesthetics through the Update to the algorithm responsible for generating colors for usernamesThe previous system has been replaced with one based on HSLuv, following the specifications of the XEP-0392 standard. Although this standard originated in the XMPP world, Pidgin has decided to apply it globally throughout the application. This ensures that the colors assigned to users are perceptually uniform and legible, avoiding low-contrast combinations that hindered readability in previous versions.
In addition, it is mentioned that the work done on this new experimental version has been intensive and has focused on cleaning and optimizing the libpurple library. A relevant technical change is the eRemoval of the specific add-on for KWallet. After conducting several tests, the Developers verified that KWallet's native integration with libsecret made the old plugin redundant. By removing it, the code is simplified and credential management is entrusted to modern Linux desktop standards, reducing the project's maintenance burden.
In addition to code cleanup, In-depth adjustments have been made to how the application handles security and internal data. Credential providers, such as KeychainAccess and wincred, have been updated to use internal account identifiers for lookups, instead of relying on usernames, which brings greater robustness to the system.
On the other hand, it is also highlighted that Several obsolete components have been removed, such as the SQLite history adapter and the Purple.Gio API, which indicates that they are preparing the ground for a lighter and more efficient codebase for the final version 3.0.0.
Finally, it's worth mentioning that the development cycle has faced human challenges, with the team acknowledging periods of burnout that have slowed progress more than desired. Despite this, The project continues to move forward with a clear roadmapThe next experimental version, 2.95.0, is scheduled for March 31, 2026. Due to the unstable nature of these test versions, packagers of the various Linux distributions have been expressly requested to refrain from including these builds in the stable repositories for end users, as the software is not yet ready for a production environment and could generate an unmanageable load of technical support requests.
Finally, and importantly, we reiterate that this experimental version is not recommended for everyday use, but rather to support developers in detecting errors and making improvements.
If you are interested in knowing more about it, you can consult the details In the following link.