g3ner1c/qb-bot

quizbowl discord bot

Languages and frameworks

Knows a bit of

Wants to learn

qb-bot's Issues

Deploy on Heroku

Docs?

maybe after v1.0.0 idk

Add powers to tossups

Set up production enviroments for development and release versions

Potential DDoS

Over the past few days, I've noticed unusually high traffic on the /api/check-answer endpoint, where some AWS instance would repeatedly check the same answer ~300 times a second. I've added a 20 requests/4 seconds rate limit to all api endpoints and blocked the spammy IPs for now. If a higher rate is needed, then I can increase the rate limit.

I'm wondering if this repository could be the cause, since it's the only repo I'm aware of that uses the endpoint, and the check_answer function appears in while True loops.

Make setting up config easier

Tell user if filter doesn't exist

"No answer" is not negged on prompts after interupt buzzes

bot negs user for incorrect answer after tossup finishes

Add tk sessions

Buzzes should still be powers even on power mark

Show where user buzzed in tossup

Resolve the need for duplicated code in question sessions

Class based and object oriented refactoring

Might be a potential idea for v2 or when things get more complex

QB Reader's official python library isn't asynchronous (as well as not being maintained), so writing an asynchronous library is a possibility.

Tossup timeouts exit tk sessions

Combine tossup responses with answerlines into one message

Update qbreader api answer checking

QB Reader recently updated their API endpoint for check-answer

see qbreader/website#81

Migrate from `requests` to `aiohttp`

Unit testing

Show filters in pk and tk session stats

No answers should neg before tossup is done reading

Use QB Reader's `api/check-answer` in response parsing