-
-
Notifications
You must be signed in to change notification settings - Fork 975
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
[kemonoparty] Post revision unlisted downloads #4706
Comments
|
My mistake, it doesn't loop indefinitely but instead downloads 12 different revisions for the post in the above picture - that's in line with what the API is returning. Kemono is only listing 2 on the actual page which is strange. Wonder if the webpage is only displaying the oldest and newest, or not showing duplicates. Is there a way to return the highest and lowest revision IDs in the config using formatting? I don't use an archive. |
The webpage is definitely showing more than 2 for other posts and is not hiding duplicates. For your post, the API lists 12 items I'd guess this is an error on kemono's side. |
Thanks, ended up assuming that later shortly after. Took @a84r7a3rga76fg's advice and started using an archive to dedup the revisions. |
A SHA1 hexdigest of other relevant metadata fields like title, content, file and attachment URLs. This value does NOT reflect which revisions are listed on the website. Neither does 'edited' or any other metadata field (combinations).
…f#5013) A SHA1 hexdigest of other relevant metadata fields like title, content, file and attachment URLs. This value does NOT reflect which revisions are listed on the website. Neither does 'edited' or any other metadata field (combinations).
Using the new revisions extractor option appears to cause a loop when downloading. Config below:
It downloads the lastest post successfully, but loops indefinetly afterward for all subsequent revisions.
The revision id's in the above image also don't exist for that post, so I'm not sure where they're being pulled from.
The text was updated successfully, but these errors were encountered: