Planet Psi

Remko Tronçon: Mimicking Jaiku with Psi

2008-05-02T18:34:32+00:00

The day before yesterday, Peter Saint-Andre sent out a couple of Jaiku invites to all Jabber Google Summer of Code students and their mentors, including me. Never having looked at microblogging before, I toyed around with it a bit, and it quickly reminded me that I still had something on my Psi wish-list for a while now: a flat, live log of all Jabber events in your network. Since I had a long weekend, I quickly coded up a prototype, and hooked it into Psi.

The result looks a bit like this:

If you know Jaiku, you’ll probably notice that this looks very similar to the Jaiku web interface. Besides status messages, there are all kinds of (extended) presence events from your contacts, such as the currently playing tune or his/her current mood. Groupchat (`channel’ in Jaiku) and directed messages are interleaved with the events, and get a hyperlink which, when clicked, opens up the corresponding groupchat or chat dialog. This type of event log allows you to have a good overview of everything that is happening in your Jabber network. And if your log gets cluttered with groupchat events, you can always disable groupchat events (or any other type of event) at the top of the dialog, with a more compact log as a result. Finally, just as with the Jaiku Jabber bot, you can quickly reply to the last event from a certain user at the bottom of the dialog.

When will this prototype be production-ready, you ask? Well, I’m actually not planning to invest any more time in it in the near future. The reason is that Aleksey Palazchenko (aka AlekSi) will create a brand new history system for Psi for his Google Summer of Code project. I’m pretty sure his new history system will enable us to get a global live history of events, together with filtering based on type. And if we still need some extra functionality, we could always create a plugin.

Remko Tronçon: Improving Psi’s roster

2008-05-01T09:21:35+00:00

For a while now, Psi users have been requesting several changes and additions to the roster (or `contact list‘). These requests include grouping contacts into meta-contacts, nested roster groups, and displaying user avatars in the roster. We have been postponing all these changes to the roster as much as possible, because none of us wanted to touch the roster code, for reasons I’ll explain below. This year, Psi is fortunate enough to have Adam Czachorowski (aka Gislan), a student from the Google Summer of Code, to work on roster improvements.

So far, the major cause of all Psi developers staying clear from doing substantial roster changes is probably the fact that all roster-related classes are very tightly coupled to each other. This has several consequences:

It’s hard to get a good understanding of which piece of code does what, since there is no separation of logic between the different classes, and none of them work without the other one.
The code is very fragile: if you change one tiny piece, you might break something completely different. Moreover, it’s hard to tell what you broke, since the functionality is spread out across the different classes.
The code is untestable: Since there is no decent separation of the roster logic (i.e. the structure of the roster) and the roster user interface (i.e. how it is shown), it has been impossible so far to create some form of automated tests for the roster code. Because of the tight coupling between the various classes, it is impossible to test each part of the roster functionality in isolation, making unit testing impossible. Given that the roster is the most central part of the Psi user interface, it is actually unacceptable that we have no form of testing whether it (still) functions correctly.
There can be no reuse of any of the roster code in other parts of the UI (such as the list of participants in the MUC dialog), or even for other IM clients that are based on the back-end of Psi.

Because of these fundamental issues, a complete makeover of the roster code is in order. More specifically, we want to have a clear separation of anything that has to do with UI, and the actual logic of the roster. Additionally, we want the (untestable) UI layer to be as thin as possible, pushing as much down to the logic layer as we can. Finally, we want to achieve a full coverage of the logic layer using only unit tests.

What Gislan will exactly do in his Google Summer of Code project still has to be worked out in detail. He will be responsible for a major part (if not all) of the roster rewrite, and get some new functionality in there as well (since that will be a breeze with the new code). You can follow his progress on his blog, and get more detailed technical information on the project page for his GSoC project.

Aleksey Palazchenko: GSoC: application details

2008-04-27T11:00:44+00:00

Abstract

Psi is one of the best XMPP-clients today, but it's current history system is lack of features. My project is its redesign and reimplementation. In more details:

more usable UI;
implementing history for groupchat;
implementing server-side history (XEP-0136).

Adam Czachorowski: First post!

2008-04-23T13:14:18+00:00

This monday I’ve got an email from Google, saying that my GSoC application was accepted! During summer, I’ll be working on Metacontacts support and various roster improvements in Psi and my mentor will be Remko Tronçon, under the XMPP Standards Foundation umbrella.

I’ll try to blog here about this project as often as possible to keep community informed and possibly get some positive feedback. I’m new to blogging, so it might be painful for me to write and for you to read first few posts, but I’ll do my best not to bore everyone to death

My accepted application is available here. If you have any comments or suggestions on that, let me know! I’d really like to know what do you think about this project. I’ll add some additional information about my plans for upcoming weeks within next few days.

And if you’re wondering who I am and/or how to contact me, take a look at this page or just contact me at jabber or e-mail (both: gislan (shift-2) utumno.pl)

Kevin Smith: Summer of Code ‘08

2008-04-22T21:15:41+00:00

As summer 2008 approaches, students have been busy applying, the XSF has been busy scoring applications, and mentors have been busy preparing. It’s time again for Google’s Summer of code, a scheme to pay students to work on open source code for the summer, and hopefully for them to continue contributing afterwards. This year has [...]

Pawel Wiejacha: Accepted into Google Summer of Code!

2008-04-22T16:09:04+00:00

I am happy to announce that I've been accepted for Google's Summer of Code 2008.

I've never managed to keep up with a blog. Well, I have a personal diary that no one knows about :D. I didn't want to keep technical blog to promote myself. I'm also too boring person to entertain my potential readers with non-technical entries.

Now I've created blog. I'll be posting GSoC related entries here. Maybe I'll come to like blogging.

I'll be working for XMPP Standards Foundation (XSF) this summer. The abstract of my proposal is available here. In few words: I'm going to make Psi prettier. It will have themable chat dialogs with XHTML-IM support and contact's extended presence (e.g. mood, user tune etc.) changes logging.

I never realized how big an event GSoC truly is, until today when I got 300 emails (students' introductions) from gsoc-students mailing list. I am just one of 1125 students who will work to improve over 175 FLOSS projects.

I'm glad to be a part of this year's Summer of Code.

Aleksey Palazchenko: My last hours...

2008-04-21T15:59:27+00:00

http://tinyurl.com/553qfa
#gsoc at FreeNode is totally madness.

UPDATE: I'm in. I'm a GSoCer now. Yesss!

Aleksey Palazchenko: One week

2008-04-13T13:46:11+00:00

One week has passed since students’ application deadline. One week before announcement and start of “community bonding” period. I think this is little bit worrying time for all students.

Kevin Smith: Psi-0.12-RC2

2008-04-01T20:55:20+00:00

Just late enough in the day that people will believe this isn’t an April’s fool, the Psi team are delighted to announce the release of Psi-0.12-RC2, fixing all blocking bugs found in RC1. Download sites are: Mac: http://downloads.sourceforge.net/psi/Psi-0.12-RC2.dmg Windows: http://downloads.sourceforge.net/psi/psi-0.12-RC2-win32.zip Source: http://downloads.sourceforge.net/psi/psi-0.12-RC2.tar.bz2 If no issues are found, we’ll go gold in a couple of weeks.

Aleksey Palazchenko: First blog entry for SoC

2008-03-31T16:45:23+00:00

Application was sent. Waiting for comments.

Aleksey Palazchenko: Resume for Google's Summer of Code

2008-03-26T07:52:06+00:00

Palazchenko Aleksey
(Nicknamed Alek Silverstone or AlekSi for short)
21 years old. Student of Moscow Institute of Electronic Technology.

Aleksey Palazchenko: Google's Summer of Code

2008-03-26T07:51:31+00:00

My resume for SoC
Blog entries (RSS feed)

Kevin Smith: Psi 0.12-RC1 released

2008-02-23T13:07:40+00:00

Hi all,
After only a little over four months since 0.11’s release, the Psi team are delighted to announce that we’ve got the first release candidate prepared for the 0.12 release. This is a great step towards a more regular release cycle, which we’re sure everyone will appreciate, but this does not mean that 0.12 will be lacking in the new and cool. Recognising that Psi’s user interface could be more usable at times, the majority of our changes for 0.12 revolve around usability. Please see the README for full release details, but probably the most important are:

Tabbed MUCs.
Tabbed chat has been very well received in previous releases, but has only gone to highlight just how badly tabbed groupchat/muc was needed, so we’ve gone ahead and implemented this. Those of us who’ve been using this new feature for a while can’t understand quite how we did without it, and various options are available for you to tweak exactly whether mucs and chats are tabbed together, or seperately, or not at all.

Improved roster search.
The roster search function has been improved, and will now filter the roster down to only matching contacts, making it much easier to find your contacts in the list.

Bookmarked conferences.
MUCs/groupchats can now be bookmarked (subject to server support, which almost every server has), so the user interface provides quick access to favourite mucs, and also to autojoin settings at login time.

Advanced option exposure.
While we’re confident our default settings will work for most of our users, we know how much many of you like to tinker with settings and to tweak Psi to be uniquely yours. Now all the options in Psi have been converted to a new internal format which allows us to provide access in the UI to every option. Those of you familiar with Firefox’s about:config will no doubt feel at home here, and will find the options in the Advanced tab of the options window (be warned that, of course, these options are only intended to be changed if you’re sure of what you’re doing and with a recent config backup, some of these may not be for the faint of heart).

We’d like to thank all the contributors, including those who’ve submitted patches for us, tested for bugs, fixed bugs, supported other users and translated Psi, and anyone else who helps the project in any way.

Now, please, go forth and test:
Mac: http://downloads.sourceforge.net/psi/Psi-0.12-RC1.dmg
Windows: http://downloads.sourceforge.net/psi/psi-win32-0.12-RC1.zip
Source: http://downloads.sourceforge.net/psi/psi-0.12-RC1.tar.bz2

Yours in Psi,
/K

Kevin Smith: Psi 0.11 released

2007-10-15T18:30:16+00:00

After over a year of hard work, we are thrilled to finally release 0.11. A lot of stuff happened over all this time, including a complete rework of the codebase to support the newest Qt4 library. Some of the changes in 0.11 include:
* Reworked account registration process (including proper support for XEP-0077 (In-band registration))
* Finished support for XEP-0004 (Data Forms) by supporting forms in messages. (thanks to Roelof Naude)
* Added support for JEP-0070 (Verifying HTTP Requests via XMPP).
* Customizable shortcuts (thanks to Ephraim)
* Added spell checking (thanks to Ephraim). Currently only aspell is supported on non-Macs.
* Added option to automatically set the resource (using the hostname)
* Added new default Stellar3 iconset
* Added support for JEP-138 (Stream Compression)
* Added support for using JEP-33 (Extended Stanza Addressing) to multicast messages to multiple users. Use option.enable-multicasting to enable it.
* Added ‘Show status message’ toggle. There is a hidden option to put status messages under the nickname (at the cost of 2 extra pixels when no status message is shown)
* Support for Bookmark Storage (JEP-0048), where bookmarked conferences are auto-joined. No UI is provided for creating bookmarks (yet).
* Better error messages, including error condition mappings (JEP-0086)
* Support dynamically changing priority
* Improved PGP error messages
* Hiding the deprecated protocol selector for service discovery by default. Use option.ui.show-deprecated.service-discovery.protocol-selector to re-enable it.
* New options system (see options.xml)
* Receiving support for vCard-Based Avatars (JEP-0153)
* Support for Multi-User-Chat (JEP-0045)
* Preliminary support for User Nickname (JEP-0172)
* Preliminary support for Roster Item Exchange (JEP-0144)
* Psi now uses the Qt4(>=4.2.3) and QCA2 libraries, replacing the Qt3 and QCA1 requirements.
* “Privacy List” support in the account dialog.
* Support for JEP-0050 (Ad-hoc commands)
* Preliminary support for JEP-0163 (Personal Eventing Protocol)
* Preliminary support for JEP-0146 (Remote Controlling Clients)
* Large parts of the codebase have been restructured.
* Fixed a chat room bug where subject/topic changes were not shown.
* Mac OS X builds are now universal binaries, supporting the new Intel based Macs.
* Support for JEP-85 (Chat State Notifications).
* Support for JEP-0115 (Entity Capabilities).
* There is now a config.xml option to make some windows use the brushed metal theme on Mac OS X.
* Window opacity support is now present for all three supported platforms.
* Fixed Unicode URL opening bug #510
* Auto-reconnect accounts on wakeup
* Copy-pasting with emoticons now works
* Fixed issue #263 where emoticons would disappear in a reply or quote
* History index is rebuilt faster
* Configure toolbars merged into main preferences dialog
* Moving tooltips
* MingW32 compiler support (Coupled with the open source Qt4 Windows library this now allows completely free building of Psi on Windows)

There’s not much else to say here that isn’t said in the release notes / readme, which everyone is encouraged to read before upgrading.

To get your latest copy of Psi, just click on one of the links below.

Windows installer:
http://downloads.sourceforge.net/psi/psi-0.11-win-setup.exe

Mac image:
http://downloads.sourceforge.net/psi/Psi-0.11.dmg

Source:
http://downloads.sourceforge.net/psi/psi-0.11.tar.bz2

Other archives:
http://sourceforge.net/project/showfiles.php?group_id=14635&package_id=53260&release_id=545913

Other packages will trickle in as they’re available, I know that Suse packages are ready thanks to Nikolay Derkach.

Translations will be coming in shortly.

Thanks to everyone who’s contributed to this (or past) releases.

Happy release time

Remko Tronçon: Introducing Greem

2007-10-14T13:45:20+00:00

After a short hiatus, I finally resumed work on my new Jabber/XMPP client project, which I christened `Greem’. The main goal of the project is to create a mobile Jabber/XMPP client for the Qtopia platform. The nice thing about Qtopia is that its target audience keeps on expanding: besides running on the GreenPhone (of which Trolltech was kind enough to provide me with one), Qtopia has recently been ported to the Neo 1973 (OpenMoko), and even Windows CE and Windows Mobile. In this post, I briefly describe what the expectations and the goals are for Greem, and how Psi fits into the picture.

The goal of Greem is to be a clean, simple Qt/Qtopia client, built completely from scratch, using lessons learned from the Psi project. Since it is my intention to keep Greem as simple and clean as possible, some advanced features from Psi will not be available: multiple accounts, customizations that are only relevant to 1% of the population, … However, development will be focused on things that Psi also needs in the near future:

Clean, unit testable APIs.
New and improved roster (for meta-contacts, avatars, …)
Server-side message archiving
Reliable communication
Simplicity

A lot of this will either flow directly back into Psi (which should be possible thanks to the decoupled APIs), or will be used as a guide to refactor certain parts of Psi that need it (e.g. the roster).

For the first release(s), not every part of Greem will be written from scratch, though. Although I already have a major part of the low-level XMPP server connection handling coded up, Greem will initially use Iris as its backend for connecting to a server. Anything beyond the connection (i.e. XMPP data structures, stanza handling, …) will be done outside of Iris. This way, the major focus can be on the front-end and general frameworks, without having to worry about the low-level implementation details (which can typically be a big hassle to get right). In the future, the Iris backend, which is connected through a very thin layer with the front-end, will be replaced by my own implementation of XMPP streams.

An update on the current status of the project will follow soon, together with some preliminary screenshots.

Remko Tronçon: Testing Psi

2007-10-01T08:00:16+00:00

While the last bugs are being squeezed out of Psi 0.11’s release candidates, work on 0.12 has already begun. One thing I’m excited about as a developer is the fact that we’re making the Psi codebase `testable’, which has some nice consequences.

The first part of our effort to make Psi testable is creating unit tests for most of our classes (using CppUnit), which should provide quick checks that our classes behave (and keep behaving) the way they should. However, the fact that Psi was not designed to be testable from the ground up makes this a non-trivial job, requiring quite some refactoring. This is something that will happen incrementally over time. A side effect of this refactoring will be an increase in modularity, allowing us to use different frontends (e.g. Cocoa) for the same code.

The second part we’re working on is creating UI tests for parts that are not automatically testable. For this, we are decoupling all our dialogs from the rest of the application, such that we can create a standalone application that allows you to toy with the dialog. This decoupling not only means that it becomes very easy to test dialogs with your own scenarios (without having to start Psi, connect to a server, …), but also means that the dialogs become completely reusable for other applications.

We still have a long way to go until every part of Psi is testable (either automatically or not), but I am very much looking forward to the day where all of our code is nicely decoupled, and we can run make check on every commit to ensure that we didn’t break anything silly.

Kevin Smith: Psi 0.11-RC3 released

2007-09-25T03:15:09+00:00

It’s release candidate time. This should be the last RC3, touch wood.
Psi-0.11-RC3 is out, please grab your copies from:

Source: http://downloads.sourceforge.net/psi/psi-0.11-RC3.tar.bz2
Mac: http://downloads.sourceforge.net/psi/Psi-0.11-RC3.dmg”
Windows: http://downloads.sourceforge.net/psi/psi-win32-0.11-RC3.zip”

Known Issues:
A very small number of users (currently only one that we know of reproducably) are affected by a crash in this version of Psi; we’re working on trying to track this down and fix it but have decided to not delay the release of 0.11 any further for it, as it will work fine for the vast majority of users. However; if you use Psi in an absolutely mission-critical environment, it may be safest to continue to use 0.10 until the bugfix is applied.

Please test; if no show-stopping bugs are revealed in the next few weeks, we’ll go gold. The changelog since 0.10 is as follows:

* Reworked account registration process (including proper support for XEP-0077 (In-band registration))
* Finished support for XEP-0004 (Data Forms) by supporting forms in messages. (thanks to Roelof Naude)
* Added support for JEP-0070 (Verifying HTTP Requests via XMPP).
* Customizable shortcuts (thanks to Ephraim)
* Added spell checking (thanks to Ephraim). Currently only aspell is supported on non-Macs.
* Added option to automatically set the resource (using the hostname)
* Added new default Stellar3 iconset
* Added support for JEP-138 (Stream Compression)
* Added support for using JEP-33 (Extended Stanza Addressing) to multicast messages to multiple users. Use option.enable-multicasting to enable it.
* Added ‘Show status message’ toggle. There is a hidden option to put status messages under the nickname (at the cost of 2 extra pixels when no status message is shown)
* Support for Bookmark Storage (JEP-0048), where bookmarked conferences are auto-joined. No UI is provided for creating bookmarks (yet).
* Better error messages, including error condition mappings (JEP-0086)
* Support dynamically changing priority
* Improved PGP error messages
* Hiding the deprecated protocol selector for service discovery by default. Use option.ui.show-deprecated.service-discovery.protocol-selector to re-enable it.
* New options system (see options.xml)
* Receiving support for vCard-Based Avatars (JEP-0153)
* Support for Multi-User-Chat (JEP-0045)
* Preliminary support for User Nickname (JEP-0172)
* Preliminary support for Roster Item Exchange (JEP-0144)
* Psi now uses the Qt4(>=4.2.3) and QCA2 libraries, replacing the Qt3 and QCA1 requirements.
* “Privacy List” support in the account dialog.
* Support for JEP-0050 (Ad-hoc commands)
* Preliminary support for JEP-0163 (Personal Eventing Protocol)
* Preliminary support for JEP-0146 (Remote Controlling Clients)
* Large parts of the codebase have been restructured.
* Fixed a chat room bug where subject/topic changes were not shown.
* Mac OS X builds are now universal binaries, supporting the new Intel based Macs.
* Support for JEP-85 (Chat State Notifications).
* Support for JEP-0115 (Entity Capabilities).
* There is now a config.xml option to make some windows use the brushed metal theme on Mac OS X.
* Window opacity support is now present for all three supported platforms.
* Fixed Unicode URL opening bug #510
* Auto-reconnect accounts on wakeup
* Copy-pasting with emoticons now works
* Fixed issue #263 where emoticons would disappear in a reply or quote
* History index is rebuilt faster
* Configure toolbars merged into main preferences dialog
* Moving tooltips
* MingW32 compiler support (Coupled with the open source Qt4 Windows library this now allows completely free building of Psi on Windows)

Justin Karneges: Installing the StartCom root into Debian/Ubuntu

2007-09-18T01:15:37+00:00

For whatever reason, the ca-certificates package of Debian/Ubuntu does not contain the StartCom root certificate. This may have changed by the time you read this article, but otherwise you’ll probably want to add this root yourself. Here is how to do it the “right way”.

First, securely get a hold of the StartCom root certificate. One easy way to do this is to use Firefox 2.0 to visit this page, and right-click save-as on the StartCom Root CA link. It is important that you save-as on the file, because otherwise Firefox will try to import the CA into its own storage and not actually save it to a file like you want. It seems like it would be even simpler to just extract the StartCom root from Firefox’s own storage, since it is already present on your local machine, but I can’t figure out how to do that. Save the file as startcom.crt.

sudo mkdir -p /usr/share/ca-certificates/startcom
sudo cp startcom.crt /usr/share/ca-certificates/startcom/
sudo dpkg-reconfigure ca-certificates

In the reconfigure application, choose Ask mode, and select the startcom certificate to have it enabled. You might also take this moment to disable the weird CAs in there. I have no idea how or why Debian decided to trust the CAs that they do. Personally, I enable only the mozilla certs and the startcom cert.

That’s all! StartCom is installed. Now it should work with Psi and Subversion, among other programs.

(Credit to Ralf Hildebrandt for the dpkg-reconfigure hint.)

Justin Karneges: QCA and Smartcards

2007-08-21T08:30:12+00:00

In public key cryptography, it is critical to keep your private key, well, private. One of the major features of QCA 2.0 is support for smartcard devices, and these devices allow convenient and safe storage of private keys. Smartcards perform cryptographic operations in hardware, never revealing the keys to the requesting computer. Traditionally, smartcards have a “credit card” form-factor and require a reader device, but today there also exist smartcards which have the form-factor of a USB mass storage device (they are not “cards” at all). The term “smartcard” can apply to either kind of device, as can “smart token” or simply “token”.

Since QCA has a pluggable backend system, changing out software algorithms for hardware calls is easily possible by writing a proper plugin. However, there is much more to using smartcards than simply substituting a private key call. Smartcards may not always be present in the computer, and may contain many stored keys. QCA offers complete smartcard support, allowing you to discover available smartcards, track inserts and removals, enumerate keys on the devices and prompt for PINs, all using a friendly Qt-based API.

The QCA distribution contains an example application called CMS Signer. It exists mainly to demonstrate using keys from smartcards in a GUI application, although it also works with on-disk keys. CMS, or Cryptographic Message Syntax, is a standard format for storing various types of secure payloads. In the case of the CMS Signer application, the CMS format is used to store digital signature data created from X.509 certificates (fun fact: S/MIME email consists of CMS-formatted parts wrapped in MIME). It is possible to configure and use smartcards completely within the CMS Signer GUI, and I’ll demonstrate this below.

First, we need a smartcard. For this article, I’m using an ePass2000 USB device.

I don’t necessarily recommend it, as I’ve not managed to get it to work under non-Windows operating systems. However, it is cute and it works, and the Windows drivers are available online for free (I find this very convenient, as I’ve managed to misplace the drivers to some of my other smartcard devices…). Most important of all though, is that it supports the PKCS#11 standard. This means the device should be compatible with all other software also supporting the PKCS#11 standard, such as Firefox and QCA.

In CMS Signer, there is a place to perform PKCS#11 configuration.

In here, we must set the path to the PKCS#11 DLL file (on other platforms this may be a .so or .dylib file). For the ePass2000, this is C:\WINDOWS\system32\ep2pk11.dll. There are also some other low-level options you can set, but generally the defaults should be fine. The PKCS#11 provider plugin for QCA was written by Alon Bar-Lev, and it makes use of his pkcs11-helper library, which is where most of these options come from.

It is unfortunate that this configuration step is needed at all, but there is currently no known or standard way to locate a user’s desired PKCS#11 DLL files. You would have to perform a very similar configuration step in Firefox as well.

Now that the drivers are configured, it should be possible to browse for our smartcard.

We can then choose a key:

The key is then imported into a local keyring. It is important to keep in mind that only the public portion of the key is imported. The private portion is not extractable from the smartcard. We can select this key to be used for signing, and enter some data to sign:

… and hit the Sign button, which prompts for a PIN:

… and now the CMS-format signature is generated:

CMS Signer can also perform signature verification, as long as the Text and Signature fields are filled. Since they are filled at this time, we can immediately verify the signature after signing.

Looks good.

Both Psi 0.11 and KDE 4 use QCA. In the future, expect to see smartcard support in these projects.

Remko Tronçon: Qtopia Greenphone Grant

2007-08-15T07:30:13+00:00

A month or 2 ago, I applied for the Qtopia Greenphone Innovation Grant Program, an initiative from TrollTech to promote the development of applications for their Linux-based Qtopia Greenphone. I probably won’t surprise anyone by saying that I sent in a proposal about writing a good, cross-platform, mobile Jabber/XMPP client. Anyway, I was very excited to receive a mail from TrollTech yesterday, stating that my proposal was accepted by their review panel! As an applicant, I will be receiving a shiny new Greenphone, together with a Qtopia SDK to develop against. Deadline for submitting my application: October 31st. Let the coding begin.

Kevin Smith: Psi 0.11-RC2 released

2007-07-15T19:57:21+00:00

It’s release candidate time.
Psi-0.11-RC2 is out there to be tested, please grab your copies from

Source: http://downloads.sourceforge.net/psi/psi-0.11-RC2.tar.bz2
Mac: http://downloads.sourceforge.net/psi/Psi-0.11-RC2.dmg”
Windows: http://downloads.sourceforge.net/psi/psi-0.11-RC2-win32.zip”

We also have a new Linux build, available from
http://downloads.sourceforge.net/psi/psi-0.11-RC2-linux-x86-bundle.tar.bz2
If untarred in / it’ll go into /opt/psi-0.11-RC2, but it’s of course recommended to untar somewhere safe, and move it yourself. It can then be executed with /opt/psi-0.11-RC2/psi. This is still slightly experimental, so please report any issues.

Please test this to destruction. If no show-stopping bugs are revealed in the next few weeks, we’ll go gold. The changelog is as follows: