Hello, and thanks in advance for any help. I want to set up a lightweight IRC server, and ngircd seems perfect. I can't find some documentation on certain things, however... for example, in the README it says
"Implemented IRC-commands are:
ADMIN, AWAY, CHANINFO, CONNECT, DIE, DISCONNECT, ERROR, HELP, INVITE, ISON, JOIN, KICK, KILL, LINKS, LIST, LUSERS, MODE, MOTD, NAMES, NICK, NJOIN, NOTICE, OPER, PART, PASS, PING, PONG, PRIVMSG, QUIT, REHASH, RESTART, SERVER, SQUIT, STATS, TIME, TOPIC, TRACE, USER, USERHOST, VERSION, WALLOPS, WHO, WHOIS, WHOWAS."
However, I can't seem to find the syntax for any of these! I tried using help, but that just brings up MIRC's help.
There are a couple of things I'd like to do at the moment, but am unsure of how, for example: I made a persistent room, and want to make myself the operator of it. I used /oper to make myself an irc admin, but /mode #channel +o myname gives me a 'you are not channel operator name.' I can't see in the server logs where to set this, and it seems odd that despite being an irc operator, I can't just force the mode command.
If there is a place where things like this are documented more thoroughly I'd lvoe that. Otherwise, I'd deeply appreciate any help you Jon
Jonathan Coveney jcoveney@gmail.com wrote:
There are a couple of things I'd like to do at the moment, but am unsure of how, for example: I made a persistent room, and want to make myself the operator of it. I used /oper to make myself an irc admin, but /mode #channel +o myname gives me a 'you are not channel operator name.' I can't see in the server logs where to set this, and it seems odd that despite being an irc operator, I can't just force the mode command.
set "OperCanUseMode = yes" in ngircd.conf.
If there is a place where things like this are documented more thoroughly I'd lvoe that.
It is in doc/FAQ.txt, is there any other place where this should be documented as well?
Hmm, I feel dumb. I thought I looked over that, I suppose I misunderstood or somesuch. I think FAQ is fine, although more instructive errors in the server could be useful. Perhaps a verbose error server option...for example, if you try to use /mode and are an oper but OperCanUseMode is not set, it could say "You can't do this because this value isn't set."
In general, more robust errors like that would be great. if you type /wallops, it yells at you what the proper syntax is. I don't know how much effort this would involve (although the number of commands is small), but in general just some basic usability stuff like that would be awesome. I'd even be willing to help!
Jon
2011/6/21 Florian Westphal fw@strlen.de
Jonathan Coveney jcoveney@gmail.com wrote:
There are a couple of things I'd like to do at the moment, but am unsure
of
how, for example: I made a persistent room, and want to make myself the operator of it. I used /oper to make myself an irc admin, but /mode
#channel
+o myname gives me a 'you are not channel operator name.' I can't see in
the
server logs where to set this, and it seems odd that despite being an irc operator, I can't just force the mode command.
set "OperCanUseMode = yes" in ngircd.conf.
If there is a place where things like this are documented more thoroughly I'd lvoe that.
It is in doc/FAQ.txt, is there any other place where this should be documented as well?
Jonathan Coveney jcoveney@gmail.com wrote:
if you try to use /mode and are an oper but OperCanUseMode is not set, it could say "You can't do this because this value isn't set."
I guess we might also change the deafault to 'yes'. But sending a more specific error message is certainly doable as well.
In general, more robust errors like that would be great. if you type /wallops, it yells at you what the proper syntax is. I don't know how much effort this would involve (although the number of commands is small), but in general just some basic usability stuff like that would be awesome. I'd even be willing to help!
Doing this should be fairly simple. Should be enough to add a new, more specific error constant, e.g.
#define ERR_WALLOPS_NEED_MSG "461 %s %s :requires message text as argument"
and then have IRC_WALLOPS() use that instead of the default ERR_NEEDMOREPARAMS_MSG.
Hi All!
Am 21.06.2011 um 23:38 schrieb Florian Westphal:
Jonathan Coveney jcoveney@gmail.com wrote:
if you try to use /mode and are an oper but OperCanUseMode is not set, it could say "You can't do this because this value isn't set."
I guess we might also change the deafault to 'yes'.
This change would be fine with me, most probably this is what IRC operators want and do activate anyway …
But sending a more specific error message is certainly doable as well.
In general, more robust errors like that would be great. if you type /wallops, it yells at you what the proper syntax is. I don't know how much effort this would involve (although the number of commands is small), but in general just some basic usability stuff like that would be awesome. I'd even be willing to help!
Doing this should be fairly simple. Should be enough to add a new, more specific error constant, e.g.
#define ERR_WALLOPS_NEED_MSG "461 %s %s :requires message text as argument"
and then have IRC_WALLOPS() use that instead of the default ERR_NEEDMOREPARAMS_MSG.
We could do this, for each IRC command. But I doubt that it would be really useful, because most IRC clients handle the commands by themselves and generate own error messages if they don't get all parameters -- so it would only help when using "/quote COMMAND PARAMS…" in a client …
For documentation of the IRC commands see RFC 1459, 2811, and 2812. But bear in mind that the commands entered in a client are not automatically the commands that the client generates and sends to the server.
Regards Alex
-
Alexander Barton -
Florian Westphal -
Jonathan Coveney