[Pidgin] #5086: no two xmpp accounts with same screenname/domain

[Pidgin]

#5086: no two xmpp accounts with same screenname/domain
--------------------+-------------------------------------------------------
 Reporter:  rjhall  |        Owner:  deryni
     Type:  defect  |       Status:  new   
Milestone:          |    Component:  XMPP  
  Version:  2.4.0   |   Resolution:        
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by msngr):

 Replying to [comment:25 deryni]:
 > It is exactly those sorts of confusions and complications that I was
 referring to when I said "internal implications" that needed to be
 "assessed". The problem is that the normalize function is currently used
 for too many things for a change as simple as this to be the entire
 solution. I think a proper solution would involve including context to the
 normalization function (to differentiate at least between account names,
 buddy names, chat rooms, etc.) but I'm unsure what exact differentiations
 would be needed.

 I agree that the changes look more than trivial. However, this "feature"
 needs to be disabled. There are genuine use cases for this.

 As a workaround, folks that want this feature can try this. This is tested
 on the latest 2.5.4 version.

 Say username is pidgin
 Say domain is a.com
 Say connect server is (1) connect.com and (2) other.com

 1. Add an account for "pidgin" as usual for connect server "connect.com"
 2. Add another account but this time give the username something else
 (say, pidgin1) and specify connect server as "other.com". The account will
 be added but won't connect  (expected as the user name is incorrect) and
 will be disabled.
 3. Click on "Modify Account"
 4. Now change back the username from "pidgin1" to "pidgin" (the correct
 username)
 5. Save and re-enable the account

 Voila! It connects and you have the same feature set as pre-2.4.0 pidgin.
 Some code path still allows you to do this (glad that the backend is
 intact!) Enjoy!

-- 
Ticket URL: <http://developer.pidgin.im/ticket/5086#comment:26>
Pidgin <http://pidgin.im>
Pidgin