-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 "Lance A. Brown" <[EMAIL PROTECTED]> writes: > Tanner Lovelace wrote: >> The Yahoo transport on the TriLUG jabber server is almost certainly >> broken. I believe it was even installed before Yahoo made all kinds >> of changes to their protocol setup that broke things. You'd probably >> do better using Gaim or Kopete.
I would expect that the Jabber on TriLUG should be upgraded, then. The latest Yahoo! transport (and RPMS I've spun for jabber 1.4.3 at ftp://people.redhat.com/ksonney/ ) is working just fine. *grin* > To address Brian's statement: GAIM did a new release very recently to > correct Yahoo logon issues. The current problem arose *after* that > release. :-( Yahoo! has been a bit more aggressive with their changes of late. Just keeping up is sometimes a challenge. Take it from someone who's trying to keep packages updated. :) - -- - ---------------------------------- - -- Kevin Sonney -- - ---------------------------------- 1024D/320C 0336 3BC4 13EC 4AEC 6AF2 525F CED7 7BB6 12C9 Go that way, really fast. If something gets in your way, turn. -- Ski instructions from "Better off Dead" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQFALNhnUl/O13u2EskRAtgtAJ9WEvoX3qtQDT++7E6Z2YcwDRnNNwCcCvND ervGantAiIy2kxoi1PctG7Y= =MAvq -----END PGP SIGNATURE----- -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
