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

feat: random tweet intervals #15

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: random tweet intervals #15

wants to merge 2 commits into from

Conversation

cygaar
Copy link
Collaborator

@cygaar cygaar commented Dec 21, 2024

It should be possible to configure a random delay period for tweet generation. Right now this value is static which leads to a less realistic agentic experience.

@ef95023
Copy link
Collaborator

ef95023 commented Dec 21, 2024

this is a great feature that we would love to include

we only made such long intervals because the free tier of x api is incredibly limiting at 17 requests per day

we need to do more testing on rate limiting to find an optimal range for integration of RNG

do you have thoughts pertaining to these particular constraints/their communication to users

@cygaar cygaar changed the title add: random tweet intervals feat: random tweet intervals Dec 21, 2024
@cygaar
Copy link
Collaborator Author

cygaar commented Dec 21, 2024

this is a great feature that we would love to include

we only made such long intervals because the free tier of x api is incredibly limiting at 17 requests per day

we need to do more testing on rate limiting to find an optimal range for integration of RNG

do you have thoughts pertaining to these particular constraints/their communication to users

Ah gotcha, we can increase the random interval minimum threshold then. I think the ideal way to do this would be allow users to specify a range or set a range based on their api tier, but I'm not entirely sure you can detect that.

@ef95023
Copy link
Collaborator

ef95023 commented Dec 21, 2024

yeah we were initially leaning towards shorter intervals and expecting any enthusiast using this to at least have the basic plan, but we were afraid of friction for fringe/surface level tinkerers

i fully agree though that we need to implement randomness and enhance agentic experience. lets get to merging in the morning after this initial wave of traffic. perhaps also jump on a call at some point soon

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

Successfully merging this pull request may close these issues.

2 participants