Configuration

[FichteFoll]

Use YAML for configuration, parser: ruamel.yaml (persists comments and style when modifying in-place).

Latest structure proposal: https://paste.chireiden.net/q/ODbUrfpWNFcT

• split in "core" and plugin-specific config
• in core, have networks key for network configuration
• plugins should have access to global (i.e. core) and their specific plugin config, but not other plugins' (?)
• plugins should be active on selectable networks
• network-specific plugin config overrides?

• [x] general parsing
• [x] transparent parsing
• [ ] auto-reload on changes
  • [ ] detect which networks have changed by comparing against cached versions and only dis-/re-/connect those
  • [ ] provide an event for plugins they can hook

[FichteFoll]

Imo we should follow the IRC URI spec [1] of only prepending hashes for channels that start with an alphanumeric character.

[nitori]

Forgot to reference, but pr #13 added yaml config parsing.

[FichteFoll]

Note to self: Prepend # to channels in config only if they start with an alphanumeric character, as described here.

[nitori]

I actually did that, but the other way around - only prepend # if it doesn't start with any of #, &, + and ! (according to rfc), since a channel can start with non-ascii (e.g. utf-8) chars on some networks like euIRC.

[FichteFoll]

Yeah well, it's good enough. I know that ZNC uses a channel named ~#znc as partyline, which would be impossible to configure this way however. Maybe intercept the server's CHANTYPES=#&+~ message?

[nitori]

Right, but then the prepending has to be deferred to after receiving the 005 message(s) (and consequently after the 001, where I usually issued the channel join commands).