| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PeterDing-youku
|
|
|
|
|
|
|
|
|
|
Quality note for niconico
|
|
|
|
|
|
|
|
|
|
LiveLeak: support more original videos
|
|
|
|
some (old?) videos use ...mp4.h264_270p.mp4... instead of ...mp4.h264_base.mp4...
This is an addition to #4768
|
|
|
|
spelling mistake corrected
|
|
acces changed to accessing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ping-dramafever
|
|
|
|
|
|
found in http://www.americanbar.org/groups/family_law.html and
http://america.aljazeera.com/watch/shows/america-tonight/2015/6/exclusive-hunting-isil-with-the-pkk.html
|
|
|
|
|
|
|
|
|
|
|
|
passing argument
|
|
|
|
|
|
|
|
|
|
For some extractors that are hard to workout a good _VALID_URL we use very vague and unrestrictive ones,
e.g. just allowing anything after hostname and capturing part of URL as id.
If some of these extractors happen to have an video embed of some different hoster or platform
and this scenario was not handled in extractor itself we end up with inability to download this embed
until extractor is fixed to support embed of this kind.
Forcing downloader to use the generic extractor can be a neat temporary solution for this problem.
Example: FiveTV extractor with Tvigle embed - http://www.5-tv.ru/rabota/broadcasts/48/
|
|
|
|
|
|
|
|
|
|
|
