A trick I think would be useful to include here is running scrapers in GitHub Actions that write their results back to the repository. This is free(!) to host, and the commit log gives an enormous amount of detail about how the scraped resource changed over time. I wrote more about this trick here: https://simonwillison.net/2020/Oct/9/git-scraping/ Here are 267 repos that are using it: https://github.com/topics/git-s…
Scrapism
11–20 of 30 posts
Re: Scrapism
#12The "Scraping XHR" [1] explains how to inspect network requests and reproduce them with Python. I actually built har2requests [2] to automate that process!
[1]: https://scrapism.lav.io/scraping-xhr/ [2]: https://github.com/louisabraham/har2requests
Re: Scrapism
#13Re: Scrapism
#14A trick I think would be useful to include here is running scrapers in GitHub Actions that write their results back to the repository. This is free(!) to host, and the commit log gives an enormous amount of detail about how the scraped resource changed over time. I wrote more about this trick here: https://simonwillison.net/2020/Oct/9/git-scraping/ Here are 267 repos that are using it: https://github.com/topics/git-s…
Re: Scrapism
#15A trick I think would be useful to include here is running scrapers in GitHub Actions that write their results back to the repository. This is free(!) to host, and the commit log gives an enormous amount of detail about how the scraped resource changed over time. I wrote more about this trick here: https://simonwillison.net/2020/Oct/9/git-scraping/ Here are 267 repos that are using it: https://github.com/topics/git-s…
> ... for example, don't use Actions as a content delivery network or as part of a serverless application ...
> Actions should not be used for: ... any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
> You may only access and use GitHub Actions to develop and test your application(s).
https://docs.github.com/en/site-policy/github-terms/github-t...
Re: Scrapism
#16This is from 2020. Besides a small change to the "Introduction to the Command Line" section, it has not been updated. Back in 2015, the author reported using CasperJS to scrape public LinkedIn profiles. The author reported this was a PITA. Here the author recommends using WebDriver implementations, e.g., chromedriver or geckodriver, in addition to scripting language frameworks such as Puppeteer and Selenium. Is scrap…
Re: Scrapism
#17A trick I think would be useful to include here is running scrapers in GitHub Actions that write their results back to the repository. This is free(!) to host, and the commit log gives an enormous amount of detail about how the scraped resource changed over time. I wrote more about this trick here: https://simonwillison.net/2020/Oct/9/git-scraping/ Here are 267 repos that are using it: https://github.com/topics/git-s…
Re: Scrapism
#18Good guide! The "Scraping XHR" [1] explains how to inspect network requests and reproduce them with Python. I actually built har2requests [2] to automate that process! [1]: https://scrapism.lav.io/scraping-xhr/ [2]: https://github.com/louisabraham/har2requests
Re: Scrapism
#19More than half of my traffic is from bots, so I'm paying something like half my operational expenses to support them. And we've had to do a lot of work to mitigate what would otherwise be DoS attacks from badly written (or badly intended!) bots. I think that at least a tip of the hat to avoiding damage would be appropriate in a piece like this.
Re: Scrapism
#20This is from 2020. Besides a small change to the "Introduction to the Command Line" section, it has not been updated. Back in 2015, the author reported using CasperJS to scrape public LinkedIn profiles. The author reported this was a PITA. Here the author recommends using WebDriver implementations, e.g., chromedriver or geckodriver, in addition to scripting language frameworks such as Puppeteer and Selenium. Is scrap…