Posted on October 19th 2003
Changed port 6669 into 6667
Support the new MSN protocol.
For the new users:
/IRCNET ADD BitlBee /SERVER ADD -ircnet BitlBee msn.irssi.org /CONNECT BitlBee
Once connected to bitlbee type:
account add msn user@mail password account on 0
Posted on July 5th 2003
Posted on April 14th 2003
You can get a visual notification in KDE panel for newly arrived IRC messages using FlashApplet.
Posted by cras on January 21st 2003
There's some talk in irssi-dev mailing list about my plans for irssi rewrite. Take a look and comment if you're interested :)
Posted on December 23rd 2002
Scripts can crash irssi too easily, fixing that properly would require major changes. But while I was again getting annoyed at those crashes, without any easy way to figure out why and where the heap corruption happened, I started thinking and figured out that the corrupted accesses happen only through one function, when accessing perl object's _irssi pointer. So, if we only could check that address to be valid.. And then I remembered GCs could easily do that.
So, get yourself a Boehm's GC (
apt-get install libgc6-dev), GLIB2 and CVS
irssi. Make sure configure says that
GC is enabled, then
/SET perl_memory_check_level can be used to
control how well irssi checks for valid memory references. Default is
1 which should prevent at least some crashes,
2 is more slower (it
runs GC before each check) but notices most invalid
references. Whenever error occurs, you'll get a nice error message
about accessing free'd memory, with a line number to script and
Posted on December 17th 2002
There's a new mailing list now for German irssi users. See mailing lists page for more information.
Posted on November 19th 2002
Finally out. Lots of changes and fixes, including support for SSL servers (by vjt), DCC send queues (by Heikki Orsila) and better support for IRCNet !channels. This version also fixes the crash at startup with some newer distributions (eg. RedHat 8) using Perl 5.8.
Posted on November 11th 2002
Too many people have asked this, so here's the answer for everyone:
Because of some bug in CVS 1.11.2 server, if you connect with older clients and use -z option, it hangs at the end. Everything is transferred, but it just gets stuck there. So your options are: a) ignore and just hit Ctrl-C, b) upgrade to CVS 1.11.2, c) don't use -z option, d) try to get CVS authors to fix it - this is not a new problem.