Frequently Asked Questions - Known Issues

This is mainly due to the fact that the Qt's Sqlite interface uses UTF-16 to store strings in the database. The size should shrink to about half of the current size when other storage backends like postgre sql and mysql will be introduced.

Besides that, you can compress the database by rebuilding it. This requires the core to be shut down. Run the following commands:
sqlite3 ~/.quassel/quassel-storage.sqlite .dump | sqlite3 ~/.quassel/quassel-storage.sqlite.bak
mv ~/.quassel/quassel-storage.sqlite.bak ~/.quassel/quassel-storage.sqlite

Note: this method seems to be way more effective than sqlite's VACUUM function.

Thanks to al_ for bringing up that idea.

We don't currently have the manpower to maintain both the desktop and the embedded version, and the old QuasselTopia didn't keep track with the rest of the codebase. Also, recent development in the mobile space seem to suggest that the focus shifts from Qtopia (or Qt/Extended) towards Qt/WinCE and Qt/X11, both of which offer the standard Qt API. We will work on making Quassel suitable for small form factors in due time, because we do have some shiny mobile devices generously sponsored by Nokia, and we do want to use Quassel on them ourselves :)

By the way, except for UI issues (i.e. config dialogs and fonts that are too large and stuff), Quassel runs alreay sorta usable on the N810!