That said, purple3/pidgin3 (still in development) only supports for keyrings and doesn't try to do any password management on its own even though password managers fall into the "Store a password(s) behind a password" as detailed on the above page.
I am the current lead developer of Pidgin, and would like to reinforce the level of collaboration in the XMPP world. Even with Pidgin being very far behind in XMPP (and everything else) everyone has been very helpful as we're trying to catch back up and answering questions about the prosody instance we run ourselves.
Pidgin is a universal client that supports many protocols/networks including IRC, XMPP, and has additional third party plugins from stuff like Discord and Slack.
That sounds great! I literally just wrote the initial skeleton last night so there's lots of work to do so any help is greatly appreciated! I'm hoping to have something somewhat usable by the end of the month.
This is great to hear and ironically we (Pidgin) just decided that Zulip was going to be the next protocol we were going to add support for just barely 24 hours ago before all this Discord nonsense!
We've been working on our next major release for a long time now to better support modern protocols. But as an unfunded Open Source project it's hard to get things done quickly when it's a "free time" only project.
You could just use libpurple to do all the im stuff and literally just write a user interface. That said, purple 2 isn't really designed for modern chat networks, but we're trying to solve that with the still unreleased purple3.