Pidgin's developers announced the fourth alpha of Pidgin 3.0 on October 30, adding a soju plugin that discovers IRC connections and creates accounts for them. The release announcement identifies the build as 2.98.0 and warns that it is not meant for end users.
For people following the chat client's development, the useful change is automatic account setup across networks behind a bouncer. MrKeyoor has not tested the integration. The behavior described here comes from the projects' documentation.
One bouncer, several network accounts
Soju connects to upstream IRC servers on a user's behalf and supports chat history playback. It sits between a chat client and the networks that user wants to reach.
Pidgin's new plugin connects to soju's bouncer network, discovers upstream connections and creates corresponding IRCv3 accounts, routing them through soju. The release notes tie this behavior to the soju.im/bouncer-networks specification. The practical benefit is less repeated account setup when several networks sit behind one bouncer.
That distinction helps explain what to evaluate: account discovery and routing are the Pidgin changes. History playback is a documented soju capability, and this announcement alone doesn't establish how completely Pidgin handles it.
An alpha for protocol work
The project's development-phase explanation says alpha work targets stability in protocol-plugin APIs. Beta targets the user-interface APIs. Pidgin plans to guarantee API and binary compatibility at the 3.0.0 general release, so plugin developers should still allow for changes during this phase.
That makes this release useful for developers who want to examine how Pidgin represents connections managed by another service. Someone choosing a daily chat client needs a different level of assurance. The alpha label describes the intended audience, and the version number 2.98.0 should not be read as a finished 3.0 release.
There is also a concrete testing hazard. IRCv3 startup commands can now run after connection and before channels are joined, but their configuration has no user interface yet. The developers warn that sensitive information in those commands would be stored in clear text. Keep credentials out of that setting.
Pidgin lists November 26 for Alpha 5, version 2.99.0, while warning that planned work can change. The useful next check is whether subsequent releases document fuller handling of managed accounts and move the relevant APIs toward the project's stated stability guarantees.