(In reply to comment #78)
> In particular, we don't seem to
> be binding a fingerprint to a JID.
On closer inspection of libotr, it seems we are indeed binding a (remote username, local account name, protocol) tuple to a fingerprint; the API just doesn't make that obvious.
(In reply to comment #78)
> In particular, we don't seem to
> be binding a fingerprint to a JID.
On closer inspection of libotr, it seems we are indeed binding a (remote username, local account name, protocol) tuple to a fingerprint; the API just doesn't make that obvious.