If it doesn't warn to user that SD is being downloaded instead. # Finally store the URL for the retrieval. # After use a bit of possible bashism to rotate string so that the last character is in front of first character. First cut away excess data and remove enclosing quotes. # Cut away and eventually get domain to download video from. If none set in command then default to stub.mp4 You can replace the curl near the end with aria2c by using this line.Īria2c -check-certificate=false " -referer="$STUB" -o "$OUT" Wrap whatever filename you want to give in quotes if it has spaces. This is assuming you don't give it a filename in the first place.
Resulting JSON says SD where it would normally have SD/HD as the available formats and the download is SD only even with the -insecure is needed on the second curl statement as it seems that at least one of the domains to download the video from doesn't have a valid SSL certificate so curl aborted on it.ĮDIT: If you couldn't tell the default filename is $STUB.mp4 as in if the stub is 18IX9abCy it translates to 18IX9abCy.mp4.
#KISSASIAN LINK GRABBER GITHUB 720P#
For now just remove the It will automatically end up grabbing the 360p version of a 720p version isn't availabele. Download the latest version of the extension. If you were grabbing a series that only had a 360p version you can remove the I might implement a check that handles it. A javascript based chrome extension to grab the links of all the episodes in a series from the websites KissAnime KissAsian KissCartoon. I don't know what would happen if that wasn't available and wasn't tested. It assumes 720p for the video resolution. I wrote up a quick bash script that you can provide the stub to and it will retrieve the video. I still need to work out some details (like hd/ sd selection and fixing the base64) but this is what I have so far: How about generating a PowerShell/cmd/shell script to download the videos? There has been some discussion about allowing custom headers in VLC for remote playback, but it does not seem to be implemented currently. Maybe the multiple urls are a form of load-balancing?īut it is good that we can decode them I don't think IDM supports Headers outside of the browser extensions. If you resolve 4vs5osstge.buzz and jm0ywuxmiu.xyz with nslookup, you will find that they point to different ip addresses. įor example, I used 4vs5osstge.buzz for all requests, and it worked for (all of my) ~140 videos.
Still haven't been able to test HSL you don't have to use the url returned from. Looks like HydraX is going for security through obscurity. How did you figure it out? I would never have thought that a company would use something like this.
#KISSASIAN LINK GRABBER GITHUB HOW TO#
EDIT: I actually did end up figuring out how to "decode" the URL provided by Īll you have to do is move the last character in the string to the beginning and then decode it in base64.
0 kommentar(er)
