-
Notifications
You must be signed in to change notification settings - Fork 34
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
feature request: bot replies in threads #6
Comments
I believe this part of my feedback issue is relevant: #1
This could be a toggleable feature. I think having the bot start threads will result in more coherent conversations on specific topics within a single channel. That way, each request only has relevant messages in the context so the bot can accurately respond to multiple people about multiple things. In the interim, creating a thread manually is a great workaround, I'm glad it works as expected! |
Noted, thanks! |
Hi @Skrownerve, I've added this feature in the latest There are some gotchas if you're running an environment where some users are prohibited from creating public threads. If that's the case for anyone reading this you'll want to see my note in the commit: 74e9111 |
v0.1.6 is out, which adds support for this! Check it out. |
updated /stop bot command to use latest API call. Remember to populate `base_blocking` with the URL to your oobabooga API server!
@Skrownerve mentioned in #1
I personally don't use threads or see much use of them on servers I frequent, so I'm not sure what best practices are, or have a good idea if this would be a popular feature.
The bot will properly respond on a thread if someone else starts one, so the change here would be to create a thread if none exists. How excited are folks about this?
The text was updated successfully, but these errors were encountered: