Is there any reason why CTCP finger needs to give an IP address?
I mean, for normal clients, the information is basically already
availible via whois.
For privledged clients, and clients on networks with host masking,
giving that information out is probably undesirable.
If there are no
Hi folks. I've been quiet for a while, life and all that. However, I've
bumped into something that has been a bit of a sore spot for a while.
Automatic command completion in scripts. I'd, personally, like to see it
banished from the face of the earth.
If you're not familiar with the feature,
I agree with taking it out.
void
On Thu, 30 Jan 2003, Chip Norkus wrote:
Hi folks. I've been quiet for a while, life and all that. However, I've
bumped into something that has been a bit of a sore spot for a while.
Automatic command completion in scripts. I'd, personally, like to see
I've been frustrated for awhile with the fact that epic doesn't allow you to
easily modify the notify interval.
From what I can tell, epic doesn't allow you any more precision than minutes
in the notify interval, and it refuses to accept a value of under a minute.
There's a couple of things I'd
Normally I would not follow up to a request for discussion, but nsx asked
me to share why I believe in the status quo. The entirity of this message
is not a statement of policy or rules or anything of the sort with regard
to epic. It simply states my personal opinions as an epic user, and the
On Thu Jan 30, 2003; 05:42PM -0600 adm propagated the following:
I would like to see command completion go away TOTALLY.
is anyone else with me here?
but starting in scripts is a step.
I think that having it set-able would be a good step in that direction.
Certainly once it is disentangled
I'd assume that most users who would set notify_interval, would know what
they're doing, but I may be wrong.
I can certainly see the scenario in which a new user who likes to experiment,
unsuspectingly sets this to what most would consider an unreasonable value
(such as 1), but I also assume even
