Bug 57347 - Don't fail when there someone else with the same nick
Summary: Don't fail when there someone else with the same nick
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: idle (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-20 22:20 UTC by Giovanni Campagna
Modified: 2019-12-03 20:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Giovanni Campagna 2012-11-20 22:20:10 UTC
It may happen that one gets disconnected because of network issues. In that case, it takes a while for the server to disconnect the user (from 5 to 10 minutes).
During that time, connection always fails because there is already someone with the desired nick.

What other clients do, and I what I'd like idle to do, is autogenerate a suitable replacement name, such as "nick_".
Comment 1 Simon McVittie 2012-11-21 00:00:08 UTC
A subtle point to consider when implementing this: when renaming jbloggs to jbloggs_ or whatever, it's necessary to make sure that Mission Control doesn't think jbloggs_ is what we want to be called in future!

(Perhaps the awkward interaction between the 'account' parameter and the nickname in IRC will make that happen automatically, though. IRC is an irritating protocol...)
Comment 2 Danielle Madeley 2013-04-29 23:22:05 UTC
Annoyingly at the moment, you actually have to change your nick in Mission Control, so it can't be any worse.
Comment 3 GitLab Migration User 2019-12-03 20:10:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-idle/issues/43.


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.