GitHub/PyLink
3
0
Fork 0
mirror of https://github.com/jlu5/PyLink.git synced 2024-11-01 09:19:23 +01:00
Code Issues Projects Releases Wiki Activity
acdd7dbb78
PyLink/docs/technical/pmodule-spec.md

10 KiB
Raw Blame History

PyLink Protocol Module Specification

In PyLink, each protocol module is a single file consisting of a protocol class, and a global Class attribute that is set equal to it (e.g. Class = InspIRCdProtocol). These classes should be based off of either classes.Protocol, a boilerplate class that only defines a few basic things, or ts6_common.TS6BaseProtocol, which includes elements of the TS6 protocol that are shared by the InspIRCd, UnrealIRCd, and TS6 protocols. IRC objects load protocol modules by creating an instance of its main class, and sends it commands accordingly.

See also: autogen/inspircd.html for auto-generated documentation the InspIRCd protocol module.

Tasks

Protocol modules have some very important jobs. If any of these aren’t done correctly, you will be left with a broken, desynced services server:

  1. Handle incoming commands from the uplink IRCd.

  2. Return hook data for relevant commands, so that plugins can receive data from IRC.

  3. Make sure channel/user states are kept correctly. Joins, quits, parts, kicks, mode changes, nick changes, etc. should all be handled accurately.

  4. Respond to both pings and pongs - the irc.lastping attribute must be set to the current time whenever a PONG is received from the uplink, so PyLink’s doesn’t lag out the uplink thinking that it isn’t responding to our pings.

  5. Implement a series of camelCase commandServer/Client functions - plugins use these for sending outgoing commands. See the Outbound commands section below for a list of which ones are needed.

  6. Set the threading.Event object irc.connected (via irc.connected.set()) when the protocol negotiation with the uplink is complete. This is important for plugins like relay which must check that links are ready before spawning clients, and they will fail to work if this is not set.

Core functions

The following functions must be implemented by any protocol module within its main class, since they are used by the IRC object internals.

  • connect(self) - Initializes a connection to a server.

  • handle_events(self, line) - Handles inbound data (lines of text) from the uplink IRC server. Normally, this will pass commands to other command handlers within the protocol module, while dropping commands that are unrecognized (wildcard handling). But, it’s really up to you how to structure your modules. You will want to be able to parse command arguments properly into a list: many protocols send RFC1459-style commands that can be parsed using the Protocol.parseArgs() function.

  • pingServer(self, source=None, target=None) - Sends a PING to a target server. Periodic PINGs are sent to our uplink automatically by the Irc() internals; plugins shouldn’t have to use this.

Outgoing command functions

  • spawnClient(self, nick, ident='null', host='null', realhost=None, modes=set(), server=None, ip='0.0.0.0', realname=None, ts=None, opertype=None, manipulatable=False) - Spawns a client on the PyLink server. No nick collision / valid nickname checks are done by protocol modules, as it is up to plugins to make sure they don’t introduce anything invalid.

    • modes is a set of (mode char, mode arg) tuples in the form of utils.parseModes() output.
    • ident and host default to “null”, while realhost defaults to the same things as host if not defined.
    • realname defaults to the real name specified in the PyLink config, if not given.
    • ts defaults to the current time if not given.
    • opertype (the oper type name, if applicable) defaults to the simple text of IRC Operator.
    • The manipulatable option toggles whether the client spawned should be considered protected. Currently, all this does is prevent commands from plugins like bots from modifying these clients, but future client protections (anti-kill flood, etc.) may also depend on this.
    • The server option optionally takes a SID of any PyLink server, and spawns the client on the one given. It will default to the root PyLink server.

  • join(self, client, channel) - Joins the given client UID given to a channel.

  • awayClient(self, source, text) - Sends an AWAY message from a PyLink client. text can be an empty string to unset AWAY status.

  • inviteClient(self, source, target, channel) - Sends an INVITE from a PyLink client.

  • kickClient(self, source, channel, target, reason=None) - Sends a kick from a PyLink client.

  • kickServer(self, source, channel, target, reason=None) - Sends a kick from a PyLink server.

  • killClient(self, source, target, reason) - Sends a kill from a PyLink client.

  • killServer(self, source, target, reason) - Sends a kill from a PyLink server.

  • knockClient(self, source, target, text) - Sends a KNOCK from a PyLink client.

  • messageClient(self, source, target, text) - Sends a PRIVMSG from a PyLink client.

  • modeClient(self, source, target, modes, ts=None) - Sends modes from a PyLink client. modes takes a set of ([+/-]mode char, mode arg) tuples.

  • modeServer(self, source, target, modes, ts=None) - Sends modes from a PyLink server.

  • nickClient(self, source, newnick) - Changes the nick of a PyLink client.

  • noticeClient(self, source, target, text) - Sends a NOTICE from a PyLink client.

  • numericServer(self, source, numeric, target, text) - Sends a raw numeric numeric with text from the source server to target.

  • partClient(self, client, channel, reason=None) - Sends a part from a PyLink client.

  • quitClient(self, source, reason) - Quits a PyLink client.

  • sjoinServer(self, server, channel, users, ts=None) - Sends an SJOIN for a group of users to a channel. The sender should always be a Server ID (SID). TS is optional, and defaults to the one we’ve stored in the channel state if not given. users is a list of (prefix mode, UID) pairs. Example uses:

    • sjoinServer('100', '#test', [('', '100AAABBC'), ('qo', 100AAABBB'), ('h', '100AAADDD')])
    • sjoinServer(self.irc.sid, '#test', [('o', self.irc.pseudoclient.uid)])

  • spawnServer(self, name, sid=None, uplink=None, desc=None) - Spawns a server off another PyLink server. desc (server description) defaults to the one in the config. uplink defaults to the main PyLink server, and sid (the server ID) is automatically generated if not given. Sanity checks for server name and SID validity ARE done by the protocol module here.

  • squitServer(self, source, target, text='No reason given') - SQUITs a PyLink server.

  • topicClient(self, source, target, text) - Sends a topic change from a PyLink client.

  • topicServer(self, source, target, text) - Sends a topic change from a PyLink server. This is usually used on burst.

  • updateClient(self, source, field, text) - Updates the ident, host, or realname of a PyLink client. field should be either “IDENT”, “HOST”, “GECOS”, or “REALNAME”. If changing the field given on the IRCd isn’t supported, NotImplementedError should be raised.

Things to note

Special variables

A protocol module should also set the following variables in their protocol class:

  • self.casemapping: set this to rfc1459 (default) or ascii to determine which case mapping the IRCd uses.
  • self.hook_map: this is a dict, which maps non-standard command names sent by the IRCd to those that PyLink plugins use internally.

Topics

When receiving or sending topics, there is a topicset attribute in the IRC channel (IrcChannel) object that should be set True. It simply denotes that a topic has been set in the channel at least once.

(Relay uses this so it doesn’t overwrite topics with empty ones during burst, when a relay channel initialize before the uplink has sent the topic for it)

Mode formats

Modes are stored a special format in PyLink, different from raw mode strings in order to make them easier to parse. Mode strings can be turned into mode lists, which are used to both represent mode changes in hooks, and when storing them internally.

utils.parseModes(irc, target, split_modestring) is used to convert mode strings to mode lists, where irc is the IRC object, target is the channel or user the mode is being set on, and split_modestring is the string of modes to parse, split at each space (really a list).

  • utils.parseModes(irc, '#chat', ['+tHIs', '*!*@is.sparta']) would give:
    • [('+t', None), ('+H', None), ('+I', '*!*@is.sparta'), ('+s', None)]

Also, it will automatically convert prefix mode targets from nicks to UIDs, and drop invalid modes

  • utils.parseModes(irc, '#chat', ['+ol', 'invalidnick']):
    • []
  • utils.parseModes(irc, '#chat', ['+o', 'GLolol']):
    • [('+o', '001ZJZW01')]

Then, the parsed mode lists can be applied to channel using utils.applyModes(irc, target, parsed_modelist).

Modes are stored in channels and users as sets: (userobj or chanobj).modes:

<+GLolol> PyLink-devel, eval irc.users[source].modes
<@PyLink-devel> {('i', None), ('x', None), ('w', None), ('o', None)}
<+GLolol> PyLink-devel, eval irc.channels['#chat'].modes
<@PyLink-devel> {('n', None), ('t', None)}

With the exception of channel prefix modes (op, voice, etc.), which are stored as a dict of sets in chanobj.prefixmodes:

<@GLolol> PyLink-devel, eval irc.channels['#chat'].prefixmodes
<+PyLink-devel> {'ops': set(), 'halfops': set(), 'voices': {'38QAAAAAA'}, 'owners': set(), 'admins': set()}

When a certain mode (e.g. owner) isn’t supported on a network, the key still exists in prefixmodes but is simply unused.