There has been a slight shift in the roadmap of Psi. While the only goal of 0.11 was to port it to Qt4 (do i hear a booooring somewhere?), we decided to make 0.11 also fully XMPP-compliant. We therefore merged the current ‘next generation’ branch (which amongst others supports privacy lists) with the mainline development branch. A consequence of this is that other features were pulled into mainline as well (yay!), so it’s not unacceptable to start looking forward to the next release.
Fixing the remaining Qt4 issues still continues as before, but we now have to finish the last few privacy list missingnesses, and integrate the new version of Iris when it supports XMPP-1.0. While Iris and QCA development is progressing fast, Psi development will be on a lower pace the following weeks (yes, some of us have other things to do like writing PhD texts etc.). We hope to have the time to do a coding sprint in June and finish up 0.11. For the people following our NG branch: this branch is now obsolete, and will be reset to the mainline branch soon.
Is there any overview what’s needed for a XMPP-1.0 compliant client? Or is it just strict obedience of RFC3920/3921? A check-list would be good for library authors…
xmpp:astro@spaceboyz.net
Not that I know of, just strict compliance to the RFCs. For us, this means adding SASL support and resource binding to Psi, and changing the account setup UI a bit to reflect this. On top of this, we will add SRV lookups.
BOORINGGG !!!
sorry too tempting
Nah seriously, we are doing Qt4 porting too for KDE4, and it’s not always a cool job. And the new features look promising, though I never look at psi-ng branch. In fact, it been a while since I updated psi-0.11 branch (I use what I work on, Kopete)
Hmm, Privacy List is just a client feature and not implemented as JEP ? I didn’t find any JEP related to that.
The features i was talking about are mainly ad-hoc commands and remote controlling. There is also extended presence, but this will be unusable until PEP becomes standard and gets implemented in servers.
As for privacy lists: it’s in the XMPP-IM RFC, Section 10.
[...] Remko’s Post [...]
Getting Psi XMPP compliant should indeed be your first priority. But migrating to Qt 4.2 should be a priority as well, not as KDE 4 development is moving forward as never before.
Here is another suggestion for Psi too: A good, usable user interface.
That would be something!