From Seo Wiki - Search Engine Optimization and Programming Languages
|This article needs references that appear in reliable third-party publications. Primary sources or sources affiliated with the subject are generally not sufficient for a Wikipedia article. Please add more appropriate citations from reliable sources. (May 2009)|
|This article may not meet the general notability guideline. Please help to establish notability by adding reliable, secondary sources about the topic. If notability cannot be established, the article is likely to be merged, redirected, or deleted. (November 2009)|
| This article is being considered for deletion in accordance with Wikipedia's deletion policy.
Please share your thoughts on the matter at this article's entry on the Articles for deletion page.
Feel free to edit the article, but the article must not be blanked, and this notice must not be removed, until the discussion is closed. For more information, particularly on merging or moving the article during the discussion, read the Guide to deletion.
Unregistered users placing this tag on an article cannot complete the deletion nomination and should leave detailed reasons for deletion on Talk:Quassel IRC. If the nomination is not completed and no message is left on the talkpage, this tag may be removed.
A screenshot of Quassel IRC under Arch Linux using Xmonad
|Developer(s)||Quassel IRC Development Team|
Quassel IRC is based on the client-server model: The core application can be placed onto a server which is connected to the Internet around-the-clock; one or more clients then connect to the core. This way, the connection to IRC can be kept up even when all clients have been closed. The combination of screen and WeeChat as well as IRC bouncers served as example for this architecture.
There is also an alternative version available which combines core and client into one binary. This application behaves like a typical IRC client; it doesn't need separate core management for example.
Other project using this model
Quassel IRC can establish simultaneous connections to multiple IRC servers. Nicknames, away reasons and the likes are managed via identities.
To facilitate use of complex or often-used commands, aliases can be defined.
Advanced features are a "chat monitor" which displays discussions of a (configurable) selection of channels and a website preview for sites linked to in the conversation.
Quassel IRC stores the backlog into an SQLite or PostgreSQL database. When scrolling the chat view, older parts of the backlog are loaded into the chat view on-demand. This allows for effortless reading of the past discussion.
The backlog can be exported by an unofficial python script, unfortunately it requires the core to be shutdown and to have been using SQLite. Searching older discussions is not easily possible at the moment.