-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comments
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 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. |
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. |
Currently blocked on having to make a env => YAML replacement engine. I will try this next weekend. |
Should be easy with |
Thoughts for consideration:
hashbang.sh
for this orirc.hashbang.sh
?irc.hashbang.sh
for this, how can we set uphashbang.sh
in a way where IRC won't lose out on messages created on a potentialhashbang.sh
matrix serverirc.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 optionThe text was updated successfully, but these errors were encountered: