1) MSN chat network is gone (migrated to Skype)
Well the msn connection is still active and I can still login, not
sure when it will be shutdown or whether we need to drop it before
that, as there maybe users using it.
MSN itself is gone yes, but the API still exists for at least another month
for "foreign" applications - such as Jitsi. If you want to remove it from
- remove /src/net/java/sip/communicator/impl/protocol/msn
- remove /test/net/java/sip/communicator/slick/protocol/msn
- remove /lib/jml-1.0b5.jar
- remove all references to bundle-msn, bundle-msn-slick and
bundle-plugin-msnaccregwizz from /build.xml
- remove protocol-msn.jar and msnaccregwizz.jar from
However, I guess it's likely that we will remove it too before the next
2) RFE: please redirect errors to a log file instead of stderr
There are console loggers and file loggers and everything is logged in
the file, of course there are some libs that have some stderr logs and
we catch everything from java, but we are unable to do so for logs
from native code.
Isn't it common practice to print errors on stderr? If not, most of those
can easily be eliminated by changing or removing the ConsoleHandler logger
in lib/logging.properties. Log files exist anyway (~/.jitsi/log).
3) jitsi ignores LC_MESSAGES
Hum, we are using java property user.language. Not sure how java detects
this property, or is it a problem in java itself must check it.
This is a problem with Java locales. They don't support that level of
abstraction. If at all, please file a bug against Java (I know that this
would be pointless).
My understanding is that you guys want to discuss bugs first before they
are entered into the jitsi.org tracker, so here they are.
Yes, thank you.
I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.
For example, even though my XMPP jabber.org account information is
correct, I always get an error that there was an error on login. This
might be due to some error in my package, though, so I haven't reported
You can always try installing from our repo or running from source
(ant rebuild run) and test with those builds.
Or take a look into the logs or send them over.