-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap and compatibility with chrome extension #288
Comments
Hello @hubyhuby, The chrome extension is indeed quite old now. But you can use other chrome extensions to basically do the same. The idea is just to shunt the Content Security Policy headers of the website, so something like this extension: https://chrome.google.com/webstore/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden should work. There is no precise roadmap. This tool has been working for years now and is still used by many. I occasionally fix some bugs and such but I have no precise features to add right now. In the meantime, to work some other related use-cases more scale-oriented we started developing a CLI tool called minet that takes inspiration from artoo somehow (specifically the scraping DSL) and that will maybe, in the future, inject artoo into headless chrome contexts for complex tasks. |
I've updated the online docs to help people shunt CSP headers and I kinda hid the extension's documentation because it really is irrelevant at this point. |
Thanks @Yomguithereal , I am tryed things like this downloading artoo from the website, but get troubles with the .js trying to DL jquery .... : {
} |
Hi Artoo,
This project is really cool.
But unfortunately with recent website security changes , the artoo library seems to not be working on most of the popular websites.
I have tried to use the chrome extension without luck and see that there is no commits since 2018. Except for a new branch gh-pages ...
Hence my questions :
Is there a plan to make chrome extension work again ? Since it seems vitale to make this project working
Is there a roadmap / milestones you have in mind to get to a 1.0 eventually ?
The text was updated successfully, but these errors were encountered: