Closed Bug 114322 Opened 24 years ago Closed 20 years ago

respond to /ctcp finger

Categories

(Other Applications Graveyard :: ChatZilla, enhancement)

x86
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: neil, Assigned: Gijs)

Details

(Whiteboard: [cz-0.9.69])

Attachments

(1 file)

It would be nice if chatzilla responded to a /ctcp finger request instead of displaying "Unknown CTCP finger () from XaCt" in the chat window.
Severity: normal → enhancement
Summary: respond to /ctcp finger → [RFE] respond to /ctcp finger
Do we have any 'standard' reply for a CTCP finger request? OR do we just make it up? :)
http://www.irchelp.org/irchelp/rfc/ctcpspec.html Is as good a spec as you'll get. I suggest we just do something like what BitchX, irssi, or mIRC do.
Product: Core → Other Applications
It's odd you should mention irssi, since I have version 0.8.9 here and it doesn't know what CTCP FINGER is. :) I guess we could reply with the 'real name' from the whois info., idle time is as good as impossible to work out.
Attached patch PatchSplinter Review
Reply to ctcp finger with the real name (description). Haven't tried messing with idle time, but a system wide idle time would probably not be something one would be able to figure out (x-platform).
Assignee: rginda → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Attachment #194514 - Flags: review?(rginda)
Summary: [RFE] respond to /ctcp finger → respond to /ctcp finger
Comment on attachment 194514 [details] [diff] [review] Patch r=rginda
Attachment #194514 - Flags: review?(rginda) → review+
Checked in --> FIXED.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Whiteboard: [cz-0.9.69]
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: