Skip to content
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

Open
remexre opened this issue Jul 1, 2023 · 3 comments
Open

soju.im/bouncer-networks support #77

remexre opened this issue Jul 1, 2023 · 3 comments

Comments

@remexre
Copy link

remexre commented Jul 1, 2023

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.

@tarkah
Copy link
Member

tarkah commented Jul 7, 2023

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

@remexre
Copy link
Author

remexre commented Jul 7, 2023

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.

@4e554c4c
Copy link
Contributor

I'd like to take a look at doing this. My general idea of how bouncer-networks works is

  1. Client connects to the bouncer and completes registration
  2. Client requests list of servers and a notification stream for server changes
  3. Client opens a new connection for each server and requests BOUNCER BIND during registration

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants