#346 new enhancement

Put users into qualified namespace.

Reported by: mjoseph Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 1.1.1dev
Keywords: jabber groupchat namespace nick Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:


Say you have a user on your roster such as:

user1 [user1@…]

And you join a groupchat call foo-chat@…. Now if that user is also in the group chat (and they selected user1 as their nick), they would show up as:

user1_ [user1=foo-chat@…]

A little annoying naming, but workable (since the chat would be using a different context wrt the server). However, let's say user2@… is not on my contact list. Now they show up in the channel as:

user2 [user2=foo-chat@…]

It can be somewhat confusing to not know if the user2 i'm talking to is the real one or the conference one. I would propose an option to qualify the pseudo-users with the groupchat that they are part of. Perhaps just don't strip the =foo-chat, such as:

user2=foo-chat [user2=foo-chat@…]

Another option would be a general-purpose mechanism for specifying a prefix-map to qualify user names that could work for various networks, such as:{jabber} =>{jabber} => 'an.' =foo-chat@…{jabber} => 'fc.' {AIM} => 'aim.'

Then, usernames could be mapped as:

user1@… --> user1 user1@… --> an.user1 user1=foo-chat@… --> fc.user1 AIM buddy: user1 --> aim.user1


Attachments (0)

Change History (0)

Modify Ticket

as new The ticket will remain with no owner.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.