Welcome, Guest. Please login or register.

Author Topic: Jabberwocky 1.4 Released  (Read 2715 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Floid

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 918
    • Show all replies
Re: Jabberwocky 1.4 Released
« on: January 06, 2004, 01:41:53 AM »
Your ability to bridge to an external service (MSN, Yahoo, AIM) depends on the transports installed on the server you use.  (Er, or the transports installed on other servers that you can discover/connect to through the server you use, I think.  Whew!)

In theory, this is one of the awesome things about Jabber.  Only a few people should have to worry about upgrade (or lockdown-workaround) bingo, and the 'common users' should never have to worry about their software.

In practice... I get the impression (perhaps malformed?) that the Jabber transports see less maintenance than conventional "let's just bung all sorts of code into one monolithic program" attempts like Trillian.  Which is an incredible shame, but considering the services that want to block 3rd-party clients can easily ban Jabber servers by IP (few addresses, versus the large cloud of Trillian users), perhaps it's to be expected.

Anyone manage to bridge to Yahoo! Messenger successfully?
 

Offline Floid

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 918
    • Show all replies
Re: Jabberwocky 1.4 Released
« Reply #1 on: January 07, 2004, 03:47:15 AM »
Quote
I used to access Yahoo through Jabber on my old
1200, surprised the hell out of my friends. It
didn't quite work 100% (I didn't show up to my
buddies as "available" IIRC), but definately a
nice and capable program.


Ah, that could be a limiting factor, though Jabber is *supposed* to be able to pass that sort of metadata/state information through if the transport is smart enough...  (I notice there might be a new libyahoo or something, which the Jabber transports probably depend on... so maybe it's 'fixed' or improved again.  Biggest problem I had - using various UNIX clients, maybe 3 months ago - was false positives from the transport I was using; it was hard to say when I'd properly logged in to the transport, and/or if the transport was actually properly talking to Yahoo.)  

The real solution is to convince all your friends to ditch the proprietary crap (and efforts to track it - note that I'm not very hot on Trillian, considering it's a 'band-aid' over the centralized services' attempts at user lock-in) and move to pure/native Jabber. ;)

For those looking for some crossplatform action (AmigaOne or Pegasos *NIX users, anyone with Windows, MacOS or anything else with TCL/Tk), I may as well mention Tkabber and The Coccinella, both of which look nice, even though I've never tried them.  (Wish I'd found them before I installed Qt just for Psi, which just doesn't float my boat for some reason.  Too much effort put into looking like ICQ.)