[prev] [thread] [next] [lurker] [Date index for 2003/09/28]
* Earle Martin <hates-software@xxxxxxxx.xxx> [2003-09-27 23:46 +0100]:
> [BitchX's quit messages]
Not to mention the fact that it has bloody stupid default settings.
(Okay, Gavin already mentioned them.) Perhaps things like "auto-kick
after too many nick changes" and "auto-kick after too many /me statements
because they look like a CTCP flood" and "auto-kick someone who just
deopped three people because the BitchX authors are paranoid and worried
they they'll be next" and {rest skipped for brevity} are all well and good
in actively hostile IRC environments, but they're really annoying in more
friendly places.
> 23:23 <@Kake> You could just configure it.
> 23:23 <@Kake> But I keep saying this, and nobody ever does.
That's because it's impossible to figure out how to do it. BitchX is
"documented" in about twelve different places, most of those being hidden
somewhere or other on the web. I used to use BitchX. I tried to figure
out how to stop it from misbehaving. I ended up deciding it was easier to
switch IRC clients than figure out how to configure BitchX. I suppose
it's easier to write quit messages than consistent documentation.
--
...computer contrarian of the first order... / http://aperiodic.net/phil/
PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2
--- --
If the code and the comments disagree, then both are probably wrong.
-- Norm Schryer
--- --- --
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52