Menu
▾
▴
#3 wish: multiple accounts under a single nickname
Again, I'll refer to everybuddy, as it was what I used prior to discovering gabber. It would be nice to have multiple accounts appear under a single nickname (sort of like treating nicknames as a group). A number of my friends have accounts on ICQ and AIM, for example, and having their names show up multiple times is a little odd.
Possibly, this should be handled by Jabber? I don't know.
"Jabber is the solution to you having multiple accounts, not your friends" is what we were told by jer at one point. So I dunno, we'll see. Maybe someday. :)
I was once a real advocate of this. But am no longer. I too used Everybuddy for a very long time before discovering Gabber. But it was sometimes quite difficult to send a message to an offline user and make sure it went to the correct UIN when there were many UIN's or Screen Names under one Handle. I prefer being able to specify "User (Home)" and User (Work) then having them all under one handle.
Of course, we all know that people can login multiple times with jabber, all under different resources... It may be possible, once we get resources working, to make multiple services act similarly, but as needo said, this could get annoying if not handled properly.
Changed to WONT FIX for now.
Logged In: YES
user_id=9539
I'm really having a tough time coming up with a decent way
to handle this UI-wise. Everybuddy has many problems in this
area.
Logged In: YES
user_id=541
I think the basic idea is almost like a nested group -- I
would like to have multiple accounts (even multiple Jabber
accounts) under the same name. The difference between just a
simple sort of nested group is that you want to send a
message to this name, and not worry about its contents. The
problem is what happens when the contact has multiple
accounts online at once -- how does Gabber decide who to
send the message to . . .
There should probably be a default hierarchy, like,
descending order of client functionality -- and within a
protocol, maybe increasing idle time. Of course, for
one-on-one chats, after the initial message, it just keeps
sending to the same protocol, but if idle time were used for
priority, normal messages could be sent to different
accounts or protocols.
That bit seems easy enough. Now, the fun part is . . . you
can rearrange the order of the accounts for each name. So,
if a particular person prefers to use MSN, you just drag
their MSN account to the top of their account list.
Simple, no? Mwahahaha!
The ugly part is that this would have to be stored on the
client side, which means I'm back to copying a config file
everywhere again.
Also, I hope my explanation makes it clear that this is
independent of resources (which is not the way it was in my
mind when I initially submitted this wish).
I still haven't solved the offline messaging bit, though --
I don't really do that often, so I haven't thought on it.
Logged In: YES
user_id=9539
Again, though, that seems overly complex, and as you said,
the issue gets even harder once the user is offline. Gabber
doesn't support resource to the fullest extent that I want
yet. Having Gabber support resources *and* this, which is
essentially *another* entire set of resources would become
way too complicated. I opt to keep Gabber simpler when
issues like this arise.
Logged In: NO
Sort of along the same lines, but I prefer a different
solution, just seeing an icon next to each name that lets me
know what transport they're using. (example of what I mean
at: http://www.geocities.com/dpandre/jajc.png )