Artoo, the client-side scraping companion(medialab.github.io)
medialab.github.io
Artoo, the client-side scraping companion
http://medialab.github.io/artoo/
10 comments
Great work! I really like this! I typically use the JavaScript console bookmarklet for tasks like this, but it is not specifically designed for scraping. I would love to see an option that would allow Artoo commands to be packaged into a PhantomJS script. Developers could use Artoo manually to figure out what elements should be targeted and then the PhantomJS script to run it in an automated fashion.
This would indeed be nice and this is precisely what we intend to code next.
What advantages does this have over Phantom.js[1] ?
[1] http://phantomjs.org
[1] http://phantomjs.org
Both are really different. Phantom.js is a headless browser while artoo is a tool to easily scrape data from website.
But combining both would be nice to make it possible to automatize scrapers that have been developed quickly directly in the browser with artoo.
But combining both would be nice to make it possible to automatize scrapers that have been developed quickly directly in the browser with artoo.
This is awesome. I've been dreaming about this for weeks.
I don't know if it is possible, but could this run as a Chrome Extension, in a background script, loading various pages, executing code on then and keep going, storing the data at the extension's localStorage?
It could also store the code of the scrapers, for reusing.
I don't know if it is possible, but could this run as a Chrome Extension, in a background script, loading various pages, executing code on then and keep going, storing the data at the extension's localStorage?
It could also store the code of the scrapers, for reusing.
Well, I see you already have almost all I suggested. Now I would want something to make the ajaxSpider render the pages using the browser engine, instead of just getting pure HTML.
This is an interesting point. I created an issue on the github repository concerning this matter. Maybe you'd like to comment on it about your use case so we can improve the tool?
I would like to see something that helps create useful, specific scrapers for languages like Ruby and Python.
It's annoying to have to run scripts multiple times, tweaking it after each run to get exactly what you need. It's a waste of time...
It's annoying to have to run scripts multiple times, tweaking it after each run to get exactly what you need. It's a waste of time...
>> ipython
[In 1]: from pyquery import PyQuery as pq
[In 2]: pq("http://www.foo.com")("<some jquery selectors>")
... or do it with requests + lxml.etree, or whatever you want
when you have what you need, copy and paste into a file
PERFECT! Thanks a lot =-)
This is in direct conflict with another library: http://artoo.io
Might be better to use another name?
Might be better to use another name?
Another "Artoo" http://artoo.io/
Yeaaaah you might wanna rename that. I think the other Artoo already has enough traction and this will just confuse people.
Still not convinced by the reasons offered for client-side scraping. If I'm on my browser, I'm not interested in consuming JSON.
Scraping is really something that's better done in the back end, and today, there are a lot of libraries that let you access web sites from Java and run all the Javascript you need in order to display the page properly.
Scraping is really something that's better done in the back end, and today, there are a lot of libraries that let you access web sites from Java and run all the Javascript you need in order to display the page properly.
To each their own. I'm not interested in systematic scraping. I just want to take back, take home the web experience I've had, and be able to digest and work with it latter. The things that I want to work with are the sights and experiences I've had. Client side is perfect.
Second, if I was trying to scrape, I'd rather do scraping with WebDriver than anything else, and injecting some client side scraping tools and using WebDriver as a driver, not a driver/scraper sounds remarkably better.
I see no reason to ever not use a browser to consume html content.
Second, if I was trying to scrape, I'd rather do scraping with WebDriver than anything else, and injecting some client side scraping tools and using WebDriver as a driver, not a driver/scraper sounds remarkably better.
I see no reason to ever not use a browser to consume html content.
For example, favoriting a tweet on twitter is lossy: there's no after-the-fact scraping I can do to know where I was, what time it was when I favorited the thing.
If we want to Publish Everywhere Syndicate to Own Site (#IndieWeb dubs this PESOS), if we want to have our own experiences we can talk about, client side is the way to go.
If we want to Publish Everywhere Syndicate to Own Site (#IndieWeb dubs this PESOS), if we want to have our own experiences we can talk about, client side is the way to go.
Skeptical at first as well coming from the good ol curl/grep/sed backend scraping world, I changed my mind considering authentication issues and instructions saving: no more need to try and auth on complex websites via phantom without knowing what actually happens, I can just log in and see in my browser what I actually wanna scrape and still rerun it later as a script.
And I just loooove listening to artoo beep over and over ;)
And I just loooove listening to artoo beep over and over ;)
Backend and frontend scraping just don't attend the same needs. Running backend monsters to scrape small to medium amount of data only once is such a drag when frontend scraping can take less than half an hour to perform the same task. Plus you can see the results of your code live while browsing the DOM comfortably. Finally, nobody prevents you from using artoo backend when you execute javascript.
Basically, it makes scraping accessible to almost anyone who can use a browser and write some CSS selectors.
This is great for simple, quick job. However, you can do only so much in a local browser itself.
I basically built a bookmarklet that let's you define the actions locally on your browser, and then run the scrapes in your own box, essentially allowing unmetered scraping without charging per page.
http://scrape.ly
I basically built a bookmarklet that let's you define the actions locally on your browser, and then run the scrapes in your own box, essentially allowing unmetered scraping without charging per page.
http://scrape.ly
closed beta?
I'm still putting the finishing touches. Will email everyone when it's ready to use.
Looks really awesome, I'll await it's arrival.
this jquery injection looks kind of dangerous. Looks like code from code.jquery.com is loaded into any page. Say I go to https://secretsquirrel.com and they have been very careful to only load javascript from their own domain but now it can also load malicious javascript from https://code.jquery.com.
it also disable CSP. i'm not exactly sure how the extension works. maybe it is turned on/off on per tab basis and defaults to off which would be quite safe. but if it defaults to on then it can be kind of risky.
it also disable CSP. i'm not exactly sure how the extension works. maybe it is turned on/off on per tab basis and defaults to off which would be quite safe. but if it defaults to on then it can be kind of risky.
jquery is injected carefully by artoo so it does not break anything on the host page. However, CSP override is not default on artoo and you have to install the chrome extension to perform this. But this extension has solely to be activated when scraping and only developers should use them while knowing its effects.