Limnoria
Limnoria copied to clipboard
progval
Separate networks share the same user and channel list
Limnoria allows us to add multiple irc networks, but those networks will share the same user and channel configuration. This is obviously not optimal, and it's become an awkward issue as our channels migrate from freenode to liberachat.
Each channel should be tightly linked to one network, and a new network should start with zero channels configured by default.
Having persistent users makes sense across networks, but each hostmask associated with a user should also be tied to a specific network.
Hi, which specific plugins / features are you concerned about?
Network-specific config variables were added in back in August 2019, though it's likely that not all 3rd-party plugins have been updated to support them yet. In particular look at the help for config channel and config network in https://github.com/ProgVal/Limnoria/blob/master/plugins/Config/README.rst#commands
Each channel should be tightly linked to one network, and a new network should start with zero channels configured by default.
That's a bit complicated, because of Limnoria's legacy. Like @jlu5 pointed out, channel-specific variables were made also network-specific somewhat recently.
However, using @config channel #chan supybot.foobar sets two variables internally: supybot.foobar.#chan and supybot.foobar.:network.#chan.
The latter is what one normally expects with the new system, as it applies to a specific channel on a single ntwork.
However, it also sets the former, which applies to all channels with this name (unless overridden by a more specific value, as defined above). This is to preserve compatibility with existing documentation and third-party plugins, which don't expect variables to be network-specific.
each hostmask associated with a user should also be tied to a specific network.
this is definitely something I'd like to do, though
Thank you for the background info. Looks like you've been working on this for a while, and I should have done more research before opening a new issue. Sorry about that!
We use ChanTracker heavily, which seems to have not been ported to the new system. I'll follow up with them.
No problem. It's not documented, so I finally got to dump that info out of my brain :)