Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

Bridge plugin #22

Closed
gdude2002 opened this issue Dec 24, 2013 · 5 comments
Closed

Bridge plugin #22

gdude2002 opened this issue Dec 24, 2013 · 5 comments

Comments

@gdude2002
Copy link
Member

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.

@rakiru
Copy link
Member

rakiru commented Dec 24, 2013

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.

@gdude2002
Copy link
Member Author

Yeah, I'm thinking that may be the way to go as well.

@gdude2002
Copy link
Member Author

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.

@gdude2002
Copy link
Member Author

This requires a rewrite. <-- note to myself

@gdude2002 gdude2002 removed this from the 1.1 milestone Aug 20, 2014
@gdude2002
Copy link
Member Author

Closing in favour of #68

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

No branches or pull requests

2 participants