Closed Bug 114322 Opened 23 years ago Closed 19 years ago

respond to /ctcp finger

Categories

(Other Applications :: ChatZilla, enhancement)

Product:
Other Applications
Component:
ChatZilla
Platform:
x86
All
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: neil, Assigned: Gijs)

Details

(Whiteboard: [cz-0.9.69])

Attachments

(1 file)

Patch
856 bytes, patch
rginda
: review+
Details | Diff | Splinter Review 
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 Patch — — Splinter 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: 19 years ago
Resolution: --- → FIXED
Whiteboard: [cz-0.9.69]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: