| Age | Commit message (Collapse) | Author |
|---|
|
Yay, now there're topic!!
|
|
Though it's kinda basic, but still
|
|
Well, an oper should have some way to manage their channel :)
|
|
User has to be authorized in order to be able to change channel's
modes.
|
|
MODE command is used to manage modes of both users and channels. But
since these tasks are quite different it'd be nice to split them to
not have an if statement whose both branches occupe whole function
|
|
SETOPER is a command for config, OPER is the one to authorize a user
|
|
So not it can show who's on the channel, yay. Though, no showing ops
|
|
Now users can query each other
Plus, server info and creation date can be changed without recompiling
using configuration file in IRC message format which is loaded on
startup
TODO: since readcfg uses IRC logic, handle() now should be able to deal
with commands ending with simply \n
|
|
Now ircd responds with all replies up to 4
Plus memchr was wrong, yep
|
|
Now there can't be single \r or \n in the message, erroneous nicks and
channel names are rejected, and usernames are stripped on '@'
|
|
Then I should make some logic for pinging others...
|
|
Yay, adding some validation to the data ^^
|
|
|
|
So, now there're all modes listed in RFC 2812. The only what they
do now, though, is a +r restricting user from changing their nick
|
|
|
|
Overall, this solution looks better. Also, now macro is better
|
|
Though they don't have modes, and JOIN/PART must be able to parse
comma separated list of channels
|