-
-
Notifications
You must be signed in to change notification settings - Fork 981
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
[Tumblr] Tumblr official API bug would cause posts being skipped in pagination #5880
Labels
Comments
fireattack
changed the title
[Tumblr] Tumblr official API bug would cause posts being missed.
[Tumblr] Tumblr official API bug would cause posts being skipped when pagination
Jul 23, 2024
fireattack
changed the title
[Tumblr] Tumblr official API bug would cause posts being skipped when pagination
[Tumblr] Tumblr official API bug would cause posts being skipped in pagination
Jul 23, 2024
#5810 might be related. At the very least it is a case where using |
mikf
added a commit
that referenced
this issue
Jul 23, 2024
restore pagination behavior from before de670bd
I made an attempt: 540eaa5 |
ghost
mentioned this issue
Jul 24, 2024
@fireattack Can you still reproduce this issue with 540eaa5? |
I didn't try; but by the look of it it should have solved it. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tumblr official API has a serious bug (tumblr/docs#76) where if some posts have same "user-set publish time" (according to their employee), using the next link returned by the API for pagination would actually skip some posts. See the original issue for a still-valid example.
And they refused to fix it.
I see gdl uses this API endpoint and
data["_links"]["next"]["href"]
, so I think I should share this as a PSA.To workaround this issue, you can use
offset
param instead of using the href provided by the API itself. (Actually, the API used to just return new href with changedoffset
, before they switched to the currentpage_number
hash fashion.)Or use
before
calculated based on posts fetched from the previous call, but make sure to include some overlapping. Because as said above, some posts would have the exactly same timestamp due to being scheduled.The text was updated successfully, but these errors were encountered: