[OTR-dev] OTR over Jabber in Gaim / Adium

[Evan Schoenberg]

Good thinking... while that wasn't the problem, detailed debug  
logging while looking for where that might happen led me to find it,  
which was that somehow gaim was getting two different objects for  
foo at jabber.org/Adium in its hash table of accounts, so  
gaim_find_account() was returning a different object than the one  
which was actually connected.  Craziness.  Fixed now, working  
great. :)  Adium 0.80 is about ready for release...  so the number of  
people using OTR will soon increase significantly.  Very exciting to  
have support built in, thanks for all your help. :)

-Evan

On Apr 28, 2005, at 5:21 PM, Ian Goldberg wrote:

> On Thu, Apr 28, 2005 at 03:13:06PM -0500, Evan Schoenberg wrote:
>
>> Hey, guys,
>>
>> I've run into a problem that I'm not quite where to begin for fixing
>> it.  When attempting to initiate OTR over Jabber in Adium, OTR throws
>> an error that
>> "You are not currently connected to [account you really ARE connected
>> to and having a chat with]/Adium (Jabber)."
>>
>> I think the problem is that the resource -- "/Adium" is making the
>> account lookup fail... but I'm not sure.  Any thoughts?  I don't have
>> otr-gaim compiled for gaim so can't test it independent of Adium, but
>> as far as I'm aware gaim-otr is responsible for all those lookups so
>> it shouldn't be Adium's fault... not that means it couldn't be.
>>
>
> It sounds like you're sometimes passing "foo at jabber.org/Adium" as the
> accountname parameter to libotr, and sometimes just "foo at jabber.org".
> libotr doesn't care which you use, so long as you're consistent.
>
>    - Ian
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
>
>