I'm making up new term: rate-limit anxiety (for APIs)
Context:
When CPython GitHub bots were still using personal access token, we were rate-limited to 5,000 requests per hour.
Now that both miss-islington and bedevere are GitHub Apps and accessing APIs using installation access token, the rate limit is increased, based on the number of users on the GitHub org , and capped at 12,500 requests per hour, relieving our rate-limit anxiety 😌
🐻 @bearcam: videos from Katmai National Park in Alaska, frequently featuring bears
🐠 @TropicalReefAquarium: a view from inside of a tropical reef aquarium in Long Beach, California
@bearcam@TropicalReefAquarium Typically I make bots that post only every 4-6 hours, but I figured since these are mostly live feeds, posting hourly makes sense? Easier to catch something interesting happening. Let me know what you think.
Also, a fun fact, adding these to https://botwiki.org brings the total number of bots on the site to 2,001 🎉
I hadn't thought of that. Back on Ex-Twitter, the goal was always to influence people (or cheat them or intimidate them), not to drive them off the platform and onto another.
I reduced the posting frequency of some of the bots I've made recently, so if you've avoided them before for being too noisy, consider giving them a try now!
@dalereardon I haven't really touched Twitter's API in months. If I remember correctly, the API for writing is now free, and you have to pay for reading? If that's the case, you might just have to scrape the data.