Re: Transports still not working in Exodus

Damon Register wrote:
> Psi was able to correctly identify the Gabber added transports but
> Exodus doesn't.  I also discovered that if I added a transport
> in Exodus, it is added correctly to Transports and then I am
> able to drag the unfiled Gabber added transports to the Transports
> group.  Before I file a bug report, I would like to hear from anyone
> if there might already be a fix or solution?  Right now I am using
> Exodus version 0.9.0.5

The problem is that there is no good way for clients to detect roster items as
transports. The way that Exodus currently uses is to treat all roster entries in
the "Transports" group as transports. Nothing more, nothing less. It's possible
(but sometimes annoying) to have the client auto-detect entries in the form of
"foo.com" and "foo.com/registered" as transports, but for some folks, this is
not always the case. The current behavior is correct, so if you want to add
something, add it as a Feature Request (not a bug). I suspect both Psi and
Gabber treat anything w/out a user part of the jid as a transport. This works
for some folks, but not all. (Especially for those of us that have services on
our roster, like: notes.jabber.org, or something similar).

pgm.