phantomjs
yt-dlp
Our great sponsors
phantomjs | yt-dlp | |
---|---|---|
17 | 2,360 | |
29,279 | 70,159 | |
- | 4.5% | |
0.0 | 9.8 | |
over 1 year ago | 5 days ago | |
C++ | Python | |
BSD 3-clause "New" or "Revised" License | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
phantomjs
-
XZ: A Microcosm of the interactions in Open Source projects
The points you make aren't unreasonable.
It is necessary to establish clear boundaries of what can and can be provided by the maintainers. If not done at an earlier stage of the project, the support burden becomes too much to bear at which point the maintainer transfers ownership, and the project suffers from catastrophic consequences such as the xz backdoor we're talking about here, or other cases where the project mostly stalls and serves as an ego-boosting platform for the new maintainer, as was the case with PhantomJS[6].
This can also happen in your life, where a "friend" sees that you possess a certain skill, and then gradually tries to push an inordinate amount of their personal work related to this field onto you.
Personally, I think it's best to use an approach with extremely clear communication as to what the maintainer can and cannot provide. This can be seen, for example, in yt-dlp[1], where the consumer is clearly informed upfront that not providing detailed information as requested will lead them to block said consumer; or sqlite where their position regarding contributed patches[2] and support[3] is similarly made clear.
Having a shouty BDFL like Torvalds can also help improve code quality[4] and questionable contributions[5], though it is better that the shouty BDFL makes statements that are professional and do not show as much aggression; so for example, "Mauro, shut the fuck up"[7] would become "Mauro, your response is completely unbecoming for a Linux kernel maintainer, and is not in line with the promise of not breaking userspace."
[1] https://github.com/yt-dlp/yt-dlp/issues/new?assignees=&label...
[2] https://www.sqlite.org/copyright.html
[3] https://www.sqlite.org/support.html
[4] https://www.theregister.com/2024/01/29/linux_6_8_rc2/
[5] https://cse.umn.edu/cs/linux-incident
[6] https://github.com/ariya/phantomjs/issues/14541
[7] https://lkml.org/lkml/2012/12/23/75
-
Show HN: Generate a concatenated file of all CSS used on a given website
Last commit was in 2019, and it uses PhantomJS to query a page, which shutdown development in 2018
https://github.com/ariya/phantomjs/issues/15344
-
youtube bandwidth throttled for cloud addresses?
Install Phantomjs and see if that improves things.
-
How to Bypass Cloudflare in 2023: The 8 Best Methods
Automated Browser Detection. Cloudflare queries the browser for properties that only exist in automated web browser environments. For example, the existence of the window.document.__selenium_unwrapped or window.callPhantom property indicates the usage of Selenium and PhantomJS, respectively. For obvious reasons, you're getting blocked if this is detected.
-
Ask HN: What's the best way to get all the HTML from a JavaScript site?
I know there is https://phantomjs.org/ but is there something else people use these days?
The issue is some websites curl works fine to get all the rendered html, but some you don't get any content without a javascript engine.
-
Detecting PhantomJS headless browsers
Despite the popularity of Puppeteer and Headless Chrome, my team of threat researchers and I wondered, to what extent PhantomJS was still being used by bot developers. In this post, we share how we identified traffic associated with PhantomJS, the types of attacks performed, and its use in comparison to Puppeteer Extra Stealth.
-
How to make a SPA SEO crawlable?
I've been working on how to make a SPA crawlable by google based on google's instructions. Even though there are quite a few general explanations I couldn't find anywhere a more thorough step-by-step tutorial with actual examples. After having finished this I would like to share my solution so that others may also make use of it and possibly improve it further. I am using MVC with Webapi controllers, and Phantomjs on the server side, and Durandal on the client side with push-state enabled; I also use Breezejs for client-server data interaction, all of which I strongly recommend, but I'll try to give a general enough explanation that will also help people using other platforms.
-
Malware/Virus protection?
Regarding youtube-dl, I remember someone mentioning they needed an external helper program called phantomjs to download from some sites. I really wouldn't recommend using phantomjs as it hasn't been updated since 2018 and I see it has known vulnerabilities too.
-
Building A Serverless Screenshot Service with Lambda
For this project we will need some extra binaries ( PhantomJS in particular) to take the screenshots. We’ll also use ImageMagick, but that is provided by AWS by default in the Lambda image, so we don’t package it separately.
-
yt-dlp release 2022.04.08
ERROR: [iq.com] apvtge3eng: PhantomJS executable not found in PATH, download it from http://phantomjs.org
yt-dlp
-
FFmpeg 7.0 Released
You can put these options in a config file and they will become the default: https://github.com/yt-dlp/yt-dlp?tab=readme-ov-file#configur...
-
Google fights Invidious (a privacy YouTube Front end)
Yep. yt-dlp and youtube-dl
https://github.com/yt-dlp/yt-dlp
https://github.com/ytdl-org/youtube-dl
Will also start to feel the impact. My theory is that we will see a bunch of new video hosting sites as youtube itself attempts to lock down its ecosystem. They haven't paid attention in any adversarial way as far as I can tell.
When they do, it wont be great.
-
XZ: A Microcosm of the interactions in Open Source projects
The points you make aren't unreasonable.
It is necessary to establish clear boundaries of what can and can be provided by the maintainers. If not done at an earlier stage of the project, the support burden becomes too much to bear at which point the maintainer transfers ownership, and the project suffers from catastrophic consequences such as the xz backdoor we're talking about here, or other cases where the project mostly stalls and serves as an ego-boosting platform for the new maintainer, as was the case with PhantomJS[6].
This can also happen in your life, where a "friend" sees that you possess a certain skill, and then gradually tries to push an inordinate amount of their personal work related to this field onto you.
Personally, I think it's best to use an approach with extremely clear communication as to what the maintainer can and cannot provide. This can be seen, for example, in yt-dlp[1], where the consumer is clearly informed upfront that not providing detailed information as requested will lead them to block said consumer; or sqlite where their position regarding contributed patches[2] and support[3] is similarly made clear.
Having a shouty BDFL like Torvalds can also help improve code quality[4] and questionable contributions[5], though it is better that the shouty BDFL makes statements that are professional and do not show as much aggression; so for example, "Mauro, shut the fuck up"[7] would become "Mauro, your response is completely unbecoming for a Linux kernel maintainer, and is not in line with the promise of not breaking userspace."
[1] https://github.com/yt-dlp/yt-dlp/issues/new?assignees=&label...
[2] https://www.sqlite.org/copyright.html
[3] https://www.sqlite.org/support.html
[4] https://www.theregister.com/2024/01/29/linux_6_8_rc2/
[5] https://cse.umn.edu/cs/linux-incident
[6] https://github.com/ariya/phantomjs/issues/14541
[7] https://lkml.org/lkml/2012/12/23/75
-
Doom Running on a Toothbrush
Or just "yt-dlp "
yt-dlp ( https://github.com/yt-dlp/yt-dlp ) still works pretty well at the current state of Twitter.
- Show HN: I create a free website for download YouTube transcript, subtitle
-
Using LangServe to build REST APIs for LangChain Applications
To download audio from YouTube videos, you'll utilize the widely used yt-dlp library, which can be installed using the pip command as follows:
- YouTube-dl has been taken down
-
Ask HN: YouTube – how to batch scrape comments and details for 300 videos?
Use: `yt-dlp with --write-comments --no-download --batch-file FILE`
- FILE is a text file with a list of YouTube id's/URL's
- https://superuser.com/a/1732443/4390
- https://github.com/yt-dlp/yt-dlp
-
Forget spaceships; I just want my music
> Then youtube-dl wasn't a thing anymore (maybe it is again?)...
yt-dlp is definitely a thing: <https://github.com/yt-dlp/yt-dlp>
What are some alternatives?
puppeteer - Node.js API for Chrome
Simple-YouTube-Age-Restriction-Bypass - A simple browser extension to bypass YouTube's age verification, disable content warnings and watch age restricted videos without having to sign in!
Nightmare - A high-level browser automation library.
tiktok-scraper - TikTok Scraper. Download video posts, collect user/trend/hashtag/music feed metadata, sign URL and etc.
slimerjs - A scriptable browser like PhantomJS, based on Firefox
youtube-dl-gui - A cross platform front-end GUI of the popular youtube-dl written in wxPython.
zombie - Insanely fast, full-stack, headless browser testing using node.js
youtube-dl - Command-line program to download videos from YouTube.com and other video sites
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
youtube-dlc - Command-line program to download various media from YouTube.com and other sites
nightwatch - Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
youtube-dl - Command-line program to download videos from YouTube.com and other video sites