-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
soju.im/bouncer-networks support #77
Comments
It appears there are still traditional ways to connect to soju w/out a custom IRC extension: https://git.sr.ht/~emersion/soju/tree/HEAD/doc/getting-started.md#other-clients |
Yep, that works as a workaround, but then the list of networks needs to be edited on the client whenever a new network is added. |
I'd like to take a look at doing this. My general idea of how bouncer-networks works is
So there are a few complications, such as whether to show the initial server (used for bouncer communication) in the UI, and also how to structure a UI for editing server info (maybe this part should come later). But in general it seems rather doable. |
The Soju bouncer has an IRCv3 capability,
soju.im/bouncer-networks
, to allow automatically creating connections to the networks that are configured in the bouncer.It would be very convenient to have support for this in halloy.
An example implementation of client support for this as a Weechat script may be found here.
The text was updated successfully, but these errors were encountered: