Dock in Mac OS X Cocoa

Hello.

There's a problem in handling dock click in Mac since Cocoa version,
because function macEventFilter is designed for Carbon, not Cocoa.
Here is an issue:
http://code.google.com/p/psi-dev/issues/detail?id=403

Attached file is a patch for handling this one. I'm not good in git,
so i send it here.
This is an adoption of this solution:
https://github.com/KDAB/Charm/blob/master/Charm/MacApplication.mm

--

-- 
Best regards, Nikolay Mikheev

A few cppcheck questions

Hi,

cppcheck found a few strange pieces of code I would like to ask
you about.

groupchatdlg.cpp:283
if (!version) {
    dlg->appendSysMsg(QString("No version information available for
%1.").arg(version->jid().resource()) , false);
    return;
}
If 'version' is not defined, ist is dereferenced one line below the check.

libpsi/tools/zip/minizip/miniunz.c:297
char rep;
[...]
if (ftestexist!=NULL)
{
    [...]
    rep = answer[0] ;
}

if (rep == 'N')

'rep' actually can be 'N' here on definition in some rare cases, no?

psiaccount.cpp:4545
void PsiAccount::handleEvent(PsiEvent* e, ActivationType activationType)
{
    if (e && activationType != FromXml) {

web service restoration & migration

Hi folks,

All Psi web services should be restored now:
  - wiki
  - forum (now Google Group)
  - issue tracker (now GitHub)

We've also changed hosting providers for the psi-im.org and planet.psi-im.org 
websites.  These systems are now under my control.  A big thanks to Hal 
Rottenberg for previously hosting these services for so many years!

Similarly, services provied by Nathan Fritz have been migrated.  His server 
was originally the home of our source repositories, which have now moved to 
GitHub.  It was also the home of the Psi MUC, which is now under my control.  
A great thanks to him for hosting these services for many years as well.

Justin

Wiki restored

The wiki is alive again: http://psi-im.org/wiki/

New account registration is disabled to prevent spam.  This may change in the 
future, but first we need to come up with a good long term plan for the 
wiki/docs.

Justin

Continuing in the cloud-y tradition, or Bug tracker and Forum

Hi folks,

As discussed earlier, we need a bug tracker.  For this purpose, we'll be using 
the GitHub issue tracker found here:
  https://github.com/psi-im/psi/issues

It looks like people had even been putting stuff in it already.  Well now it's 
official.

We also need a replacement for the web forum.  Without something like it, 
regular users don't have an obvious path to get help.  Instead of setting up a 
standard web forum again we will try a Google Group:
  http://groups.google.com/group/psi-users

The web interface to Google Groups is not the most beautiful thing, but users 
should be able to navigate it as well as any web forum I think.  It also has 
the advantage of offering a mailing list interface, which I know people here 
will like.

There will be no migration of past data into these new systems.  The Redmine 
data was lost, in fact.  As for the forum data, it may be interesting to 
restore it someday for historical purposes, but in any case it wouldn't go 
into the Google Group.

I still need to correct the links on the website that refer to these services.  
In the meantime, I've made redmine.psi-im.org and forum.psi-im.org redirect to 
the new locations.

Justin

Code moving to github

Hi folks,

I've taken the initial steps to make github the official home for our code.

https://github.com/psi-im

The psi, iris, and libpsi modules were already in there, being synced from our 
origin repos (iris was even being specially synced from svn).  I have disabled 
the syncing mechanisms for these repos now, so new commits should be targetted 
against github.  I did not perform any kind of clean reimport into github.  I 
believe there wouldn't be a difference in the final result, unless someone can 
correct me.

This means iris now uses git instead of svn.  Additionally I've moved psimedia 
into github, so it no longer uses svn either.  Also, the placement of these 
projects into an organization dubbed "psi-im" is significant.  It marks the 
start of their transition away from being under the Delta umbrella to the Psi 
umbrella.  I'll write more about this in a future email.

There are still plenty of URLs and references all over the place that point to 
the old repo locations.  I'll work to fix these soon.

Justin

P.S.: I know I'm behind on email.  I'll get to it all eventually.

Bug Report: Psi crashes when sending a message to an offline user

The crash occurs when sending a message to one of your contacts and that 
contacts goes offline at the exact moment you are sending the message. 
Although observation of the crash was accidental, you can reproduce it 
as follows:

Sender's side:
	1. Right click on a any online contact.
	2. Select the option 'Send Message To'.
	3. Select a specific resource, but do not click.

Receiver's side:
	4. Go offline in the specific resource.

Sender's side:
	5. Click to send meeting invitation .

The crash occurs because of an invalid reference access in the function 
ContactProfile::doContextMenu in contactview.cpp, line 1546.

1544	//if(res > 0) {
1545		const UserResource &r = rl[res];
1546		rname = r.name();
1547	//}

Notice that removing the comment will not really solve the problem. The 
problem is caused by rl (resource list) becoming empty before the rname 
(resource name) assignment. r is invalid.

Do you plan to fix this problem any time soon?

Psi handling of priorities of user presence

Dear Psi developers,

I have noticed that Psi handles priorities of user presence in a non 
very intuitive way, which significantly differs from the handling of the 
same scenario done by XMPP servers such as OpenFire. Consequently, Psi 
displays the wrong presence while the server shows the correct one.

Observed Situation:
If priorities of two or more resources are the same, Psi uses the last 
update from any of those resources as the current user status (which is 
not necessarily the correct one).

Scenario:
For example, given a user connected from two resources, 
a <at> b.com/resource1 and a <at> b.com/resource2, both are priority 5, both being 
initially available. If a <at> b.com/resource1 goes offline, the user a <at> b.com 
is shown by Psi as offline. This is clearly incorrect because 
a <at> b.com/resource2 is still online (as correctly shown by the XMPP server).

Interestingly, this only happens if an observer (another user) is 
present in the system. If the observer connects to the system after 
a <at> b.com/resource1 went offline, the user a <at> b.com is shown correctly as 
online (because a <at> b.com/resource2 is online).

What exactly was your original, intended design for such scenario? Is 
this a problem you plan to solve in upcoming versions? Any other comment 
on the subject?

Thanks in advance for your feedback,

Certificate Spoofing issue in PSI

Hello Psi-Maintainers,

it has bee brought to my attention (as the maintainer of the fedora-psi
package) that the currently released psi version is vulnerable to the
issues listed in the security advisory below. Mainly:

    When displaying a security dialog with a certificate, KSSL does not
    properly force its QLabels to use QLabel::PlainText. As a result, if
    given a certificate containing rich text in its fields, it will
    render the rich text.

http://archives.neohapsis.com/archives/fulldisclosure/2011-10/att-0353/NDSA20111003.txt.asc
http://www.kde.org/info/security/advisory-20111003-1.txt

I've looked at parts of the source long and hard and did come to the
conclusion that it would be way to dangerous for me to touch that part
of the code myself introducing more breakage than I would be fixing.

Is there maybe a chance to get a 0.14.1 release with (those) security
issues fixed? Or even a 0.15?

--

-- 
sven === jabber/xmpp: sven@...

Re: Psi-Devel Digest, Vol 88, Issue 2

PSI language and forum