#1243 new defect

bitlbee strips '.' from Jabber IDs

Reported by: faure@… Owned by:
Priority: normal Milestone:
Component: IRC Version: Unspecified
Keywords: Cc:
IRC client+version: Konversation 1.5 Operating System: Linux
OS version/distro: OpenSuSE 13.2


I know, I know, RFC 2812 says '.' is not allowed in IRC nicks. But that's just the theory :-)

In practice, it appears to work fine.

I made this patch and finally, after all these years, I can ping my fellow Jabber groupchat users by their real JID ("firstname.lastname") rather than pinging them with "firstnamelastname" which often doesn't trigger a notification for them.

Jabber is already complex enough with some clients showing the JID, others (like PSI I think) showing the nickname and others (like Adium) showing the full name.... we don't need bitlbee to be a 4th kind of jabber client, showing the JID without the dot :)

Tested with konversation as the IRC client, and several people in group chats having a '.' in their JID. I'm not sure if this works for users who themselves have a '.' in their JID.

If you hate the idea of this patch, I understand. I just thought I'd share it, since it works for me.

Attachments (0)

Change History (5)

comment:1 Changed at 2016-01-12T17:50:31Z by dx

This is what the translate_to_nicks setting is meant to do. Replace mentions of irc nicks with xmpp nicks. I think it would be better to fix that instead of hacking it to break the rfc. See #928.

comment:2 Changed at 2016-01-12T18:10:46Z by faure@…

I agree, fixing #928 sounds a thousand times better than my hack. Thanks for the pointer to #928.

comment:3 Changed at 2016-09-25T04:55:59Z by dx

Marked #1262 as duplicate of this.

comment:4 Changed at 2016-09-25T09:15:16Z by anonymous

FWIW, I'd like to get this fixed even if #928 is fixed. With long names, it's hard to read people's names without the period, even if translate_to_nick (which is arguably a hack) works.

comment:5 Changed at 2016-09-25T09:34:08Z by wilmer

As the person who wrote this code, I'd like to point out that "fixed" is the wrong word when you're talking about introducing an RFC violation.

It only helps a little bit that the RFC violation is likely ubiquitous, but the restriction being in place right now is *not* a bug. :-P

Modify Ticket

as new The ticket will remain with no owner.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.