Mar

26

Jabber downgrade

Tagged with , , , , , ,  

My experiment with replacing irssi with Jabber clients is over for now. There are a few reasons for this of course.

  • Mobile Jabber clients simply are not there yet. There is no way they can compete with a screened irssi over PuTTY. Notifications are nice, but the cost in RAM usage (for Java apps) and usability (for native clients) is too high.
  • 24/7 connectivity is too hard to achieve with Jabber clients.
  • I like being available on IRC at all times without people having to find out my Jabber ID or email address. This is for making myself more available, not to keep my contact information  more private (that’s not my cup of tea anyway.)

Bottom line: old school server/client solutions still rule in chat, just as I’ve found with email (IMAP) and PIM data (SyncML servers).

I still love Jabber though, and my Bitlbee session is open. Running Jabber over my irssi session may make my Jabber presence less exciting and featureful, but it also makes it client-independent and more reliable.

Comments

2 Responses to “Jabber downgrade”

  1. TabTwo on March 27th, 2008 2:13 am

    Well, one day you will learn that Jabber/XMPP is so much more than only chatting. And being loggend on to a MUC 24/7 is no problem using screen + centericq.

    Regards,

    TabTwo

  2. topyli on March 27th, 2008 2:42 am

    Thanks TabTwo. I do realize how awesome XMPP is. I also know I’m clinging to old tech with putting more weight on IRC. Chat and above all presence are just too important right now to sacrifice because of poor clients. You can’t deny the power of screened irssies on servers :)

Leave a Reply