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

Add support for chat connectors as separate microservices #64

Open
boring-nick opened this issue Feb 27, 2024 · 0 comments
Open

Add support for chat connectors as separate microservices #64

boring-nick opened this issue Feb 27, 2024 · 0 comments

Comments

@boring-nick
Copy link
Contributor

It would be very useful for certain scenarios to implement chat connectors as separate services, rather than being part of supibot. For example, supibot could be restarted without connecting all of the channels.

It could also potentially simplify the inevitable forced migration to eventsub for twitch chat connections.

Current infrastructure choice is to use Redis streams.
More information about planned connector design here: https://github.com/Supinic/supibot/tree/platform-connectors-manifest/connector-docs

Example connector for IRC: https://github.com/boring-nick/supibot-connector-poc

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

1 participant