-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix: upstream provider fixes #711
Conversation
Two of the items were removed and had to be replaced.
In which scenario does it redirect for you? |
I think we used to rewrite |
We've disabled support for Amazon Music pages because of the use of an API, but the old extraction logic was still in place. Removing it cleans up the code a bit.
We used to redirect to the Audible page for audiobooks, but that page no longer exists. Also, the Audible cover art is no longer higher resolution than the main Amazon page. Therefore, we'll simplify the image extraction and use the standard pages instead.
Upstream data has been changed to mark the first image as the main (and therefore front) image.
The audiobook page is now the same as the generic page, so the special handling of JS data extraction is no longer necessary.
Oops, then I was imply teasting with the wrong domain yesterday. This link also redirects for me. Interestingly, the larger image from our Audible test case still exists, but there seems to be no way to extract the image identifier from anywhere... |
Hmm. Hopefully we find a way to extract those again later, but for now, it's better to have a 500x500 image than to have no image at all :) |
🚀 Released 1 new userscript version(s):
|
fix: upstream provider fixes (#711)
Funnily enough, in #786, I changed the image extraction logic to use that of the physical product pages, and the old images are now in use again 😅 |
Unfixed:
Closes #697