Closed
Bug 391327
Opened 19 years ago
Closed 16 years ago
support NOIDPREFIX
Categories
(Other Applications Graveyard :: ChatZilla, enhancement)
Other Applications Graveyard
ChatZilla
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: samuel, Assigned: rginda)
References
()
Details
If there is NOIDPREFIX support indicated in the 005 message, we could somehow indicate registered vs. unregistered users.
Comment 1•19 years ago
|
||
Related to bug 388729?
Comment 2•19 years ago
|
||
From the information in the bugs, it sounds like two ways to implement the same thing (go freenode!), but since their entire website is screwed it's hard to know. It'd be nice to copy the actual details into the bug. :)
| Reporter | ||
Comment 3•19 years ago
|
||
Yes, they're apparently solving the same problem in two different ways. This bug will have some effect on tab-completion. We need to automatically remove the prefix character when matching and add it back depending on the matched nick.
Comment 4•19 years ago
|
||
This was announced two years ago but never actually enabled on Freenode as far as I can tell. Do any other networks use it?
Comment 5•16 years ago
|
||
The NOIDPREFIX spec is dated March 2006, the freenode server I connected to didn't advertise the NOIDPREFIX feature, and I can find no references suggesting anyone is actually using it - or really considering using it. It seems the basename part of the spec in particular (you register the base name and can use any extended derivative of it) was controversial, too.
Unless a network is actually using this feature (Hyperion, the freenode server software, does actually support it AFAIK but it is not enabled), I'm proposing we WONTFIX this.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Updated•1 year ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•