Closed Bug 953928 Opened 11 years ago Closed 8 years ago

XMPP and XMPP based protocols don't allow Resource name to be changed without deleting.

Categories

(Instantbird Graveyard :: Account manager, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

References

Details

*** Original post on bio 491 by Zachary <zachlr AT comcast.net> at 2010-09-05 16:20:00 UTC *** For XMPP and XMPP based protocols (like Google Talk or Facebook), if you want to change the Resource name, you must delete the account from Instantbird entirely, and create it again with the correct Resource name. The resource name should be able to be changed in the Properties dialog within Account manager, for ease of use.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows Vista → All
Hardware: x86 → All
*** Original post on bio 491 at 2010-09-06 09:53:44 UTC *** I think the resource name should not be part of the username of the account, for a few reasons: - The resource is something completely obscure for all users who are not familiar with XMPP protocol details. - The resource is not used by the server to determine which account is used. - When testing if an account already exists, the comparison is done on the "normalized account name", and this normalized name doesn't include the resource, which makes the account wizard refuse the creation of another XMPP account with the same username and server but a different resource. I've no idea of how easy or difficult it would be to make this change in the current code.
*** Original post on bio 491 at 2012-02-16 21:58:31 UTC *** This is actually fixed in our JS-XMPP implementation, but that can't fully replace the libpurple XMPP implementation yet, unfortunately.
Depends on: 955019
Fixed in JS-XMPP.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.