Summary: | telepathy-idle doesn't allow setting "username" | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Matej Cepl <mcepl> |
Component: | idle | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | enhancement | ||
Priority: | medium | CC: | jonathon |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | output of IDLE_DEBUG=all /usr/bin/telepathy-idle 2>&1 |tee /tmp/telepathy-idle-log.txt |
Description
Matej Cepl
2008-06-24 08:38:17 UTC
Setting to enhancement. I don't think this is a bug (reading any particular significance into the claimed username is a bit mad, since it's user-configurable in most clients), but it is a missing feature. Specifically, the problem is that idle always uses the same string as the nickname for the user's claimed username (used instead of the ident if they're not running an identd), while other clients use the user's real username or a user-configured string. 16:25 < smcv> so for some reason #fedora-qa allows you to join if you claim to be matej, but not if you claim to be mcepl ... 16:29 < smcv> idle ought to have a "user" parameter to RequestConnection(), probably 16:30 < smcv> it's a stupid way to do ACLs in any case, since arbitrary clients can specify whatever "username" they like - talk to the #fedora-qa chanops and get your other self unbanned? ... 16:32 < smcv> if you want to provide a patch, search idle-connection.[ch] and idle-connection-manager.[ch] for "realname" (case-insensitively) and add a similar property "user" (defaulting to a copy of nickname), then use that in irc_handshakes() I've added a 'username' param in a branch in my git repo: http://git.collabora.co.uk/?p=user/jonathon/telepathy-idle;a=shortlog;h=refs/heads/username-param Merged, will be in idle 0.1.4/0.2.0. |
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.