## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1381209-route_replies-as-a-global-user-module?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:25963790 -->
User at the very least. I load this module on every single network I add, simply because without it using multiple clients becomes an exercise in frustration.
User at the very least. I load this module on every single network I add, simply because without it using multiple clients becomes an exercise in frustration.
<!-- github-comment-id:32822340 -->
The module maintains internal state about what replies it now expects to
see and forward them to which client. This state is per-network. If to
make it loadable at user, the module will need to store several states
itself; now it's just 1 state per loaded module.
Stateless modules are much easier to make user or global...
The module maintains internal state about what replies it now expects to
see and forward them to which client. This state is per-network. If to
make it loadable at user, the module will need to store several states
itself; now it's just 1 state per loaded module.
Stateless modules are much easier to make user or global...
<!-- github-comment-id:32827556 -->
Maybe we could have a mechanism to force load a module for each user or network.
ie: turn every network module into a user module, and every user module into a global module.
Maybe we could have a mechanism to force load a module for each user or network.
ie: turn every network module into a user module, and every user module into a global module.
<!-- github-comment-id:32834877 -->
I think this was discussed somewhere and this isn't going to happen, because it's a hack fixed by https://github.com/ircv3/ircv3-specifications/issues/162.
<!-- github-comment-id:138908302 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
User at the very least. I load this module on every single network I add, simply because without it using multiple clients becomes an exercise in frustration.
The module maintains internal state about what replies it now expects to
see and forward them to which client. This state is per-network. If to
make it loadable at user, the module will need to store several states
itself; now it's just 1 state per loaded module.
Stateless modules are much easier to make user or global...
Maybe we could have a mechanism to force load a module for each user or network.
ie: turn every network module into a user module, and every user module into a global module.
I think this was discussed somewhere and this isn't going to happen, because it's a hack fixed by https://github.com/ircv3/ircv3-specifications/issues/162.