You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.
With the somewhat-completion of #19, we can start looking at this.
A configurable bridge-relaying plugin. Take chat from anywhere, on any protocol, and send it anywhere else, on any protocol (including the same one).
I don't feel like this will be difficult. A couple things to consider are related to how the configuration file is laid out - How do we differentiate usernames and channel names on protocols that don't? How do we make it a "rich" configuration without making it cumbersome?
Obviously, the config will be reloadable; I don't plan on adding configuration-by-command yet.
The text was updated successfully, but these errors were encountered:
For differentiating between users and channels, one way would be to default to channels, and have an optional field to specify the type, user or channel.
Basic bridge plugin is done - need to make a couple config changes and then add support for various protocols directly as some relaying methods will need their own formatting.
With the somewhat-completion of #19, we can start looking at this.
A configurable bridge-relaying plugin. Take chat from anywhere, on any protocol, and send it anywhere else, on any protocol (including the same one).
I don't feel like this will be difficult. A couple things to consider are related to how the configuration file is laid out - How do we differentiate usernames and channel names on protocols that don't? How do we make it a "rich" configuration without making it cumbersome?
Obviously, the config will be reloadable; I don't plan on adding configuration-by-command yet.
The text was updated successfully, but these errors were encountered: