summary refs log tree commit diff
path: root/handle.c
AgeCommit message (Collapse)Author
5 daysAdd TOPIC and t channel flag supportNakidai
Yay, now there're topic!!
5 daysAdd SETHOSTNAME commandNakidai
Also remove hostname argument from the cli. It'd be better to have it in a config file rather than passing through an argument, it was like that since times config file didn't exist, but time has changed
5 daysAdd LIST commandNakidai
Though it's kinda basic, but still
5 daysFix loop in kick()Nakidai
Incrementing global count instead of i is a stupid mistake...
5 daysFlatten privmsg to a userNakidai
Version before works fine, but - Checking whether it's a client or not is redundant - writef() was inside the loop before the break; for no good reason
5 daysAdd support for n channel flagNakidai
It's a flag that restricts a set of users able to write to a channel to those who joined. If not, reply 442 is sent upon PRIVMSG
5 daysFix KICK permissionsNakidai
IRC operators should be able to change channel modes as well
5 daysAdd KICK commandNakidai
7 daysFactor writechanf() calls out to a macroNakidai
As they will anyway repeat a lot of times, it's better to make a macro for that. Also now this look better and printing doesn't take too much attention within a block of logic
7 daysFix writechanf() in mode_channel()Nakidai
Well, prefix starts with a colon, yes...
8 daysAdd channel mode editing supportNakidai
Well, an oper should have some way to manage their channel :)
8 daysAdd authorization for mode_channel()Nakidai
User has to be authorized in order to be able to change channel's modes.
10 daysRefactor MODENakidai
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
11 daysAdd basic support for channel operNakidai
At least it is now set to a first user :D
11 daysChange way to deal with modes in channelsNakidai
I thought it'd be fine to store modes as an array. But using this is awful experience. Take a look at simple NAMES command: it just needs to check whether some user is oper or voice or not, and with that approach it will need to iterate over an array of users, and for each user iterate over an array of modes. Or it is possible to optimize it, saving all interesting modes to a local buffer and then iterating over it. But those are attempts to fix broken design So, instead of array of modes there'll be lots of fields regarding each mode or kind of mode From now on (struct Channel).peers is not a simple array of peers, but the one with metainformation. This is done by making an array of structures, so there are renames throughout the code Also, I didn't like that it was users and not peers and this is a nice opportunity to rename it: in first place this was done to avoid thing that compiler somehow could silently ignore type change, but this is also a stylistic change reflecting my view on naming
12 daysFix some typesNakidai
- One is missing * - Second is missing s
12 daysFix UB with reply 461Nakidai
It requires a parameter command, but no caller provided it :/
12 daysAdd OPER/SETOPERNakidai
SETOPER is a command for config, OPER is the one to authorize a user
12 daysFix PRIVMSG/NOTICENakidai
It's incorrect to check for an uppercase letter on a lowercase string...
12 daysAdd NAMESNakidai
So not it can show who's on the channel, yay. Though, no showing ops
13 daysAdd WHOIS and config parsingNakidai
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
2026-02-01Update READMENakidai
It wasn't very accurate for this time
2026-02-01Add validationNakidai
Now there can't be single \r or \n in the message, erroneous nicks and channel names are rejected, and usernames are stripped on '@'
2026-02-01Fix all the warningsNakidai
The one in user.c is the funniest one
2026-02-01Refactor QUIT message sendingNakidai
After seeing same announcing code second time I decided it should be done before an actual quit in loop.c. Plus, channel exiting is now done in user_remove().
2026-02-01Add ping systemNakidai
Now users will be kicked for inactivity o.o
2026-01-30Add PING command v0.1.0Nakidai
Then I should make some logic for pinging others...
2026-01-30Add support for NOTICENakidai
Well, it's the same as PRIVMSG but different name
2026-01-30Invert the logic in nick()Nakidai
Well... yes
2026-01-30Simplify join commandNakidai Perumenei
- Instead of checking users in the channel check user's channels - Ensure thing looks really dumb here, so remove it
2026-01-30Add nickname change announcementNakidai Perumenei
2026-01-30Move announcing code to writef.cNakidai Perumenei
Well, I guess that code is needed more then once, so it'll be good to move it to some function
2026-01-30Add nickname checkingNakidai Perumenei
Yay, adding some validation to the data ^^
2026-01-12Implement 443Nakidai
2026-01-10Add basic user mode handlingNakidai
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
2026-01-07Move quit announcement code to quit()Nakidai
Well, it's more appropriate for that function to handle this rather than for ircd(). Now code looks simpler, ircd() is not that complex, and support for optional quit message is present
2026-01-06Add basic channelsNakidai
Though they don't have modes, and JOIN/PART must be able to parse comma separated list of channels
2026-01-04Add codeNakidai