You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've taken a lot of inspiration from this repo; thank you so much @grishka for your amazing work 🙏 💕 🙏
The API has a specific issue where /get_followers and /get_following only ever return up to 400 users, regardless of page_size and page. So if I set page_size to 50, I can get 10 pages but only ever access up to a total of 400 users.
For users with more than 400 followers, we should be able to use the clubhouse API to access all of them in a paginated fashion, with pagination working past 400 users.
Screenshots
N/A
Smartphone (please complete the following information):
Device: macOS
OS: Catalina
Version any
Additional context
Given your extensive use of the Clubhouse API, I figured that you've probably run into this limitation and I was wondering if you were able to work around it?
Thanks!
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm the author of https://github.com/transitive-bullshit/clubhouse, an open source TypeScript wrapper around the Clubhouse API.
I've taken a lot of inspiration from this repo; thank you so much @grishka for your amazing work 🙏 💕 🙏
The API has a specific issue where
/get_followers
and/get_following
only ever return up to 400 users, regardless ofpage_size
andpage
. So if I setpage_size
to 50, I can get 10 pages but only ever access up to a total of 400 users.To Reproduce
See related bug here: transitive-bullshit/clubhouse#2 and my code implementation here: https://github.com/transitive-bullshit/clubhouse/blob/master/packages/clubhouse-client/src/clubhouse-client.ts#L289
Expected behavior
For users with more than 400 followers, we should be able to use the clubhouse API to access all of them in a paginated fashion, with pagination working past 400 users.
Screenshots
N/A
Smartphone (please complete the following information):
Additional context
Given your extensive use of the Clubhouse API, I figured that you've probably run into this limitation and I was wondering if you were able to work around it?
Thanks!
The text was updated successfully, but these errors were encountered: