Open ghost opened 10 years ago
Authentication tends to vary from server to server. While there are definitely patterns, there's no one standard; as such I've mostly been leaning towards putting authentication functionality in network-specific utility modules (e.g. kitnirc.contrib.freenode
and kitnirc.contrib.foonetic
).
That said, a generic "nickserv" module might not go amiss as another alternative for contrib/ - it'd cover cases where there isn't already a network-specific utility module, and while it wouldn't work for every network, it'd work for a lot of them.
If you were to implement the nickserv module how would implement the configs?
The following seams to fit with the existing code.
[nickserv]
nick@server = password
The configs typically don't specify server, because the way they're laid out is usually for a single server (i.e. you'd have one config per network and run a separate instance of the bot per network you wanted it on). As such, it'd probably be more like...
[nickserv]
nick = BottyMcBotters
password = hunter2
nick
could potentially be optional (and just result in a /msg nickserv identify
I don't know how much you would like to to have built in but a standard authentication module might be a good idea.
The one I wrote is a bit premature. I had a section in the config file for each host which contained nicks and passwords.
The module could look something like this