Add generic URL handling system for servers that don't support the TTVLOL API #30
Conversation
This file contains 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
|
@thinkpad4 Would it be possible to test if the config works in this version? It does on my end but I want to rule out differences between setups.
|
|
Tested the new version of twitch.py and purple works with config now. Thank you very much |
Instead of supporting each API individually allow passing a custom URL. If the URL includes "[channel]" it will be replaced with the real channel name similar to the Xtra app, otherwise defaults to the TTVLOL API. It should work as long as the API doesn't require something like a custom header or URL encoding (TTVLOL). Tested with Purple Adblock: --twitch-proxy-playlist="https://eu1.jupter.ga/channel/[channel]" and luminous native API: --twitch-proxy-playlist="https://eu.luminous.dev/live/[channel]"
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.
Instead of supporting each API individually allow passing a custom URL. If the URL includes "[channel]" it will be replaced with the real channel name similar to the Xtra app, otherwise defaults to the TTVLOL API. It should work as long as the API doesn't require something like a custom header or URL encoding (TTVLOL).
Tested with Purple Adblock: --twitch-proxy-playlist="https://eu1.jupter.ga/channel/[channel]" and luminous native API: --twitch-proxy-playlist="https://eu.luminous.dev/live/[channel]"