So BINKD is reporting a BUSY address if the AKA is on the line twice? This
doesn't seem right to me. I (or someone) should probably ask them if this is
intentional behavor.
I should be able to filter it, so that so Mystic only sends the address once.
Av> Gotta say it seems a bit strange to have to announce to the world via
Av> bink sessions an address that is bogus just so I can sort a bunch of
Av> message bases to display nicely in the index reader.
You shouldn't have to. I wonder if this is a BINKD bug?
Av> Do you think would could just get the reader to allow bases to be
Av> displayed by message groups or something similar?
Probably not. We'll see.
Groups in Mystic are not static they are calculated dynamically. One base
often has many group memberships. Most people also use a global group, some
use a "local" vs "networked" group, etc. If I were to try to sort by a "group"
it'd give odd results (many bases would be in the list more than once). This
makes it sloppy, confusing, and difficult to synchronize data between the
duplicate entries.
Address profiles are how static groups of bases are linked in Mystic, and it
has always been that way. Whats the difference between using the address to
define grouping, as opposed to any other method? The only difference is where
you do it in the editor.
The real issue here is BINKD refusing the connection which I can probably fix,
otherwise it works as expected.
