Opened 11 years ago

Closed 10 years ago

Last modified 7 years ago

#1294 closed Defect (Won't Fix)

Colloquy interprets nicks in IRC URLs as channels

Reported by: jheiss Owned by: timothy
Component: Chat Core (IRC) Version: 2.1 (Mac)
Severity: Normal Keywords: irc url
Cc:

Description

A web search for "irc url" turns up three proposals for IRC URLs:

http://www.w3.org/Addressing/draft-mirashi-url-irc-01.txt (1996)
http://tools.ietf.org/html/draft-butcher-irc-url-04 (2003)
http://www.mozilla.org/projects/rt-messaging/chatzilla/irc-urls.html (2006)

All three seem to indicate that irc://myserver/foo should generally trigger a connection to channel #foo on myserver, and Colloquy seems to do that.

However, all three provide a way to force the target to be interpreted as a nick with which to establish a private conversation. The 1996 and 2006 documents append ",isnick" to the URL, the 2003 document uses ",isuser". I.e. irc://myserver/bar,isnick or irc://myserver/bar,isuser would establish a private conversation with "bar". Colloquy does not seem to implement this. Either of those syntaxes result in a join of #bar.

Change History (3)

comment:1 Changed 11 years ago by akempgen

i'm not exactly sure this is a good idea, since "," is usually used to seperate irc channels. how do other clients handle this?

comment:2 Changed 10 years ago by zach

  • Resolution set to wontfix
  • Status changed from new to closed

comment:3 Changed 7 years ago by anonymous

IMHO a client should not join #isuser or #isnick but in stead treat the "channel" listed before it as a user.

irc://irc.example.org/bary,isnick,foo,foobar,barbar,barbara,isnick

Then it opens channels: #foo #foobar #barbar, a private conversation with barry and one with barbara

I would prefer a scheme like irc://bary@irc.example.org that just looks soh interesting. :)

Good luck,

Note: See TracTickets for help on using tickets.