You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the original assumption in the README is wrong, and .m3u8 files do not explicitly require an authentication token after the initial fetch of start.m3u8 (which itself links to an transcode-session-id-authenticated version of index.m3u8).
This issue tracks the implementation of supporting .m3u8 files in the userscript and server-side.
Detection of start.m3u8 in the userscript
Modification of start.m3u8-contained link to index.m3u8 in the userscript
Support for .m3u8 file extension server-side
The text was updated successfully, but these errors were encountered:
It seems like the original assumption in the README is wrong, and
.m3u8
files do not explicitly require an authentication token after the initial fetch ofstart.m3u8
(which itself links to an transcode-session-id-authenticated version ofindex.m3u8
).This issue tracks the implementation of supporting
.m3u8
files in the userscript and server-side.start.m3u8
in the userscriptstart.m3u8
-contained link toindex.m3u8
in the userscript.m3u8
file extension server-sideThe text was updated successfully, but these errors were encountered: