[Rohan010101]

Summary

Fixes #2168.

Update LusciousRipper to work with the current Luscious URL structure and provide an HTML-based fallback for image extraction when the existing GraphQL API is unavailable.

Changes

URL handling

• Updated the Luscious album URL pattern to support:

  • luscious.net
  • www.luscious.net
  • members.luscious.net
  • legacy.luscious.net

• Removed support for the obsolete old.luscious.net host.

• Updated URL sanitization so it no longer rewrites URLs to old.luscious.net.

• Verified that album IDs continue to be extracted correctly.

Image extraction

The existing implementation retrieves image URLs through the Luscious GraphQL endpoint at apicdn.luscious.net.

During investigation, the endpoint was found to no longer be resolvable, causing the existing API-based extraction to fail.

Inspection of accessible Luscious album HTML showed that image URLs are directly present in <img src> elements and are served from ah-img.luscious.net.

The ripper now:

1. Attempts the existing GraphQL API extraction first.
2. Falls back to extracting image URLs directly from the album HTML if the API extraction fails.

This preserves the existing API implementation while providing an alternative extraction method.

Testing

• Verified the updated Luscious URL pattern and album ID extraction.
• Verified HTML image extraction against accessible album content.
• Successfully downloaded images using the HTML fallback.
• Ran the LusciousRipper-specific test suite using Java 21.
• All LusciousRipper-specific tests passed.
• git diff --check passes with no whitespace errors.

Known limitation

Some Luscious content appears to depend on an authenticated browser/session context. Such content may remain inaccessible to RipMe when the required session state is unavailable.

Cookie/session handling was not addressed as part of this change and is considered a separate issue.