If you would like to use irssi on a remote server so that it works as proxy for pidgin, you should already have ‘server’ and ‘network’ parameters set up in your ~/.irssi/config . If you don’t know what I’m talking about, take a look here and also examine the config file. You should figure it out pretty fast how to configure irssi to do basic stuff it is supposed to do.
What you will also need is GNU screen installed on the remote server. So, what is screen? “Screen is a full-screen window manager that multiplexes a physical terminal between several processes, typically interactive shells.” Basically what you can do with it is that you can run certain processes and put them into the background (detach from them), and than later see them again (attach to them) when you want to. If you don’t know how to use screen, take a look here, or use google to find a tutorial on using screen. There is plenty of them out there. You will need screen to put the running irssi into the background on your server so that you may disconnect from the remote server after you set irrsi up.
So, after you have got your irssi configured and running under screen, you will have to load the proxy plugin for irssi, set a password for your future pidgin-to-irssi connection and bind one free port to irssi for sharing server connection. Here is how to do it:
/SET irssiproxy_password <password>
/SET irssiproxy_ports <network>=<port>
The final step is to configure your pidgin client to connect to your remote server. In pidgin, go to accounts -> manage accounts and then add a new IRC account. Fill the following parameters:
Username: <network name from your config file>
Server: <IP address or hostname of your server>
Password: <password you set for irssiproxy>
Port: <port number you used for binding>
Keep in mind that you should have your irssi running all the time on your remote server under screen for this connection to work… and, that’s all folks!