Bug 33048 - Allow to change nick in XMPP rooms
Summary: Allow to change nick in XMPP rooms
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on: 33589
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-13 00:38 UTC by Guillaume Desmottes
Modified: 2016-01-01 00:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume Desmottes 2011-01-13 00:38:19 UTC
Atm, we can't change our nick in a XMPP room. The obvious way would be to call SetAlias() using the room channel specific handle but that doesn't work.


gabble/roster-DEBUG: 13/01/2011 09:36:07.93857: gabble_roster_handle_set_name: queue edit to contact#9 - change name to "coucou"
gabble/roster-DEBUG: 13/01/2011 09:36:07.93919: roster_item_apply_edits: Applying edits to contact#9
gabble/roster-DEBUG: 13/01/2011 09:36:07.93966: roster_item_apply_edits: Changing name from cassidy-test1@jabber.belnet.be to coucou
gabble/roster-DEBUG: 13/01/2011 09:36:07.94011: roster_item_apply_edits: Contact#9 did change, sending message
wocky-DEBUG: 13/01/2011 09:36:07.94131: _write_node_tree: Serializing tree:
* iq xmlns='jabber:client' type='set' id='1055594091'
    * query xmlns='jabber:iq:roster'
        * item jid='badger@conference.jabber.belnet.be/cassidy-test1@jabber.belnet.be' name='coucou'
wocky-DEBUG: 13/01/2011 09:36:07.198498: _end_element_ns: Received stanza
* iq xmlns='jabber:client' from='cassidy-test1@jabber.belnet.be' to='cassidy-test1@jabber.belnet.be/ceb47283' id='push2947279566' type='set'
    * query xmlns='jabber:iq:roster'
        * item subscription='none' name='coucou' jid='badger@conference.jabber.belnet.be/cassidy-test1@jabber.belnet.be'
gabble/roster-DEBUG: 13/01/2011 09:36:07.198821: validate_roster_item: item node has resource in jid, skipping:
* item xmlns='jabber:iq:roster' subscription='none' name='coucou' jid='badger@conference.jabber.belnet.be/cassidy-test1@jabber.belnet.be'
wocky-DEBUG: 13/01/2011 09:36:07.199229: _write_node_tree: Serializing tree:
* iq xmlns='jabber:client' type='result' to='cassidy-test1@jabber.belnet.be' id='push2947279566'
wocky-DEBUG: 13/01/2011 09:36:07.200098: _end_element_ns: Received stanza
* iq xmlns='jabber:client' from='cassidy-test1@jabber.belnet.be' to='cassidy-test1@jabber.belnet.be/ceb47283' id='1055594091' type='result'
gabble/roster-DEBUG: 13/01/2011 09:36:07.200365: roster_item_apply_edits: Nothing to do for contact#9
gabble/roster-DEBUG: 13/01/2011 09:36:07.200483: _gabble_roster_item_maybe_remove: contact#9 is still on the roster
Comment 1 Paul van Tilburg 2011-01-18 04:48:45 UTC
Actually, something weird happens if you do /nick foo.  Nothing seems to change but if I open a chat window to some XMPP-contact and start to talk, "foo: " is prefixed as my nickname, while in the chat room my old nickname is still used.
Very confusing! :)
Comment 2 Guillaume Desmottes 2011-01-18 04:52:10 UTC
Yeah we disabled /nick on XMPP for now. See https://bugzilla.gnome.org/show_bug.cgi?id=638766
Comment 3 Jonny Lamb 2011-01-27 02:00:55 UTC
We could at least allow joining rooms with TargetID="room@server/nick" so we can specify our own nick when joining the room.
Comment 4 Jonny Lamb 2011-01-27 02:41:33 UTC
(In reply to comment #3)
> We could at least allow joining rooms with TargetID="room@server/nick" so we
> can specify our own nick when joining the room.

Maybe not actually.
Comment 5 Mattias Eriksson 2011-10-20 05:35:52 UTC
This works in pidgin with an openfire xmpp server. Pidgin implements http://xmpp.org/extensions/xep-0172.html to support this if I understand it correctly.
Comment 6 big.smile 2016-01-01 00:30:08 UTC
Any news about this bug?
Why use alias?
Why not only update presence information to the room like here: http://xmpp.org/extensions/xep-0045.html#changenick  ?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.