Repository navigation
streamwish fix vsembed - #1574
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1573
StreamWish moved playback to a new player on vsembed.com: the StreamWish hosts the plugin uses (
mainanddmca) now answer/e/<id>of a playable file with a 302 tohttps://vsembed.com/<code>, an empty JS app, so the current plugin ends in ResolverError.Changes (streamwish.py only):
/api/stream?s=<code>&ld=1(file data; nodata= removed), then/api/stream/tracking?c=<encrypted code>&ld=1, whoseX-Trackingresponse header holds the stream info as AES-CBC encrypted JSON. Key and IV are built like the player script does (fixed key, IV = fixed salt + host name in hex);resolveurl.lib.pyaescovers it.tiktok, thenhls).sources/linksscraping runs unchanged on the page that was already fetched, without a second request.vsembed.com/<code>) added to domains and pattern.Evidence:
mainanddmcaredirects a file ID to the same vsembed code; a made-up ID still gets the old "File is no longer available" page there.sourcesandlinksforms, with and without subs, with a$$referer) the patched plugin returns exactly what the current one returns.Tested in Kodi 22.0 RC2 (Linux) with InputStream Adaptive: plays with all sample links below. Without InputStream Adaptive Kodi 22 plays neither source: its FFmpeg rejects the disguised segment URLs ("not in allowed_segment_extensions").
Samples: