Modify ↓
Opened at 2013-06-18T17:50:56Z
Closed at 2013-06-22T21:50:52Z
#1067 closed defect (fixed)
Nick naming broken somewhere between 20130601 and 0617
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | devel |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: | Debian |
Description
The behavior for years has been to actually name a contact by their nick, so a nick of foo@… would be simply foo. At some point between June 01 and June 17, this convention was broken for most protocols, rendering the nick as foobarcom. Bizarrely, however, while at least xmpp and msn are affected, oscar/aim doesn't seem to be.
Attachments (0)
Change History (2)
comment:1 Changed at 2013-06-22T10:48:00Z by
comment:2 Changed at 2013-06-22T21:50:52Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
changeset:devel,994 should fix this.
Note: See
TracTickets for help on using
tickets.
Yes, I think I see what happened here. The "chop" variable in nick_gen() is still assigned but no longer used later on.
The reason OSCAR/AIM are fine is because there the handle is just the part before @, the @blah part gets added by BitlBee just to make it a complete IRC hostmask.
Will try to fix this later today.