Re:Show HN: Kizie – Twitter for web, reimagined
by unclebucknasty on Thursday September 16, 2021 @06:08PM
(#28558360)
Ah, understood. I asked because years ago I played with the Twitter API a bit and found its rate limits pretty restrictive, so was wondering if that had changed or, if not, how you were working around it.
Hopefully your users will get tons of value from the other improvements, such that these small trade-offs you have to make for rate limits are insignificant to the overall UX upgrade.
Best of luck on customer acquisition, and congrats on what you've built thus far--no small thing for a one person operation!
Re:Show HN: Kizie – Twitter for web, reimagined
by thelifeofrishi on Friday September 17, 2021 @04:37AM
(#28562788)
Thanks, appreciate it :)
And yes, you're right, there are rate-limits for endpoints in Twitter API, I've optimized the app to be in rate-limits and still be able to make the most of it.
For ex. I recently added Messages in Kizie. Twitter API's Messages endpoint has a rate-limit of 15 requests per 15 min window. Really really low for something like messages. On top of that each request returns at most 50 messages(not conversations).
How Kizie handles it is it makes 3 requests on initial load and then checks for new messages every 2.5 minutes. It was kinda tricky to do all of it reliably and I'm still trying optimise it more for better experience :)