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

Set up Dendrite-based IRC bridge #94

Open
RyanSquared opened this issue Apr 26, 2022 · 5 comments
Open

Set up Dendrite-based IRC bridge #94

RyanSquared opened this issue Apr 26, 2022 · 5 comments

Comments

@RyanSquared
Copy link
Member

Thoughts for consideration:

  • Should we use hashbang.sh for this or irc.hashbang.sh?
    • If we use irc.hashbang.sh for this, how can we set up hashbang.sh in a way where IRC won't lose out on messages created on a potential hashbang.sh matrix server
    • If we don't use irc.hashbang.sh, we need a good way to set up either SRV records or well-known, with the former being defined in admin-tools and the latter probably being done via an Ingress. I believe we can have separate Ingress on the same domain name defined across namespaces, so this should be a valid option
  • Should this be tested to see if we can use a temporary database?
  • Should we use Dendrite in monolith or polylith mode? Polylith mode probably won't give us any advantage, and given this only needs to scale to the size of the IRC server, I think the IRC server will fall over first.
@RyanSquared
Copy link
Member Author

One of the considerations was to ensure that users from the Matrix side can still create and administrate channels on the IRC side. As far as I know, this is completely working with matrix-appservice-irc. I tested this by joining #_oftc_#testingchannelhello:matrix.org and was able to get admin permissions for that room.

I do not know how well actually registering the channel from the IRC side works using this method. I think it requires a manual message to ChanServ.

@RyanSquared
Copy link
Member Author

I would like to point out that the primary reason I'm comfortable moving to a second-gen solution is because this would act as a gateway from Matrix to our IRC server. The primary point of interacting with the community since I've been in Hashbang has been the IRC server and I'd like to keep that intact and never alienate that audience, but we're growing such a large Matrix audience at this point that I feel like a bridge that is directly incorporated into the protocol is now necessary so we're not abandoning Matrix users either.

@RyanSquared
Copy link
Member Author

Currently blocked on having to make a env => YAML replacement engine. I will try this next weekend.

@daurnimator
Copy link
Member

Currently blocked on having to make a env => YAML replacement engine. I will try this next weekend.

Should be easy with yq.

@daurnimator
Copy link
Member

matrix-org/dendrite#2591

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

No branches or pull requests

2 participants