We currently have bnc<>ircd caps, and now this handles client<>ircd caps. Any capabilities can be added to the BNC core via capabilities.go in a single function. away-notify example is included.
This runs any messages sent to or from a client through any cap handlers that have registered themselves to process them. In case of the away-notify example, if the client does not support away-notify but the bnc<>ircd does, then AWAY messages to the client will be dropped. Cap handlers also have the opportunity to modify the message if needed.
Questions:
Are there any caps that would need more involvement than hijacking/modifying sent and received messages from the client?
We currently have bnc<>ircd caps, and now this handles client<>ircd caps. Any capabilities can be added to the BNC core via capabilities.go in a single function.
away-notifyexample is included.This runs any messages sent to or from a client through any cap handlers that have registered themselves to process them. In case of the
away-notifyexample, if the client does not supportaway-notifybut the bnc<>ircd does, thenAWAYmessages to the client will be dropped. Cap handlers also have the opportunity to modify the message if needed.Questions: