Instapy: [Priority Refactor] Change "scrolling"-parts to graphql
Since there now is a basic documentation about the first and basic graphQL endpoints, and an example on how to use them we are starting to refactor the way we get information from Instagram.
Once done, this will remove ~35-40% of the work we have to put into adjusting the HTML elements since the structure of the endpoints stays the same even though they change the frontend.
This is an important step towards a stable version, so I encourage everyone to support this issue by adding something to the bounty so we get this feature ASAP...
If there are any questions regarding the endpoints, feel free to ask, I think I can give some hints if there are any problems, even though they are pretty straight forward.
timgrossmann
>All comments
This is important work, but I think Instagram will notice access from specific account to the graphQL DB.
This is not recommended since we want not to get blocked.
I think we shall maintain another account that crawl throw the DB using a proxy server and save all this db to be used from real accounts.
Best solution is to use MySQL server but a 'write - read' async mechanism can also be implemented easily.
I am working in it now it is working but need many improvements.
sionking
on 17 Dec 2017
Related issues
thisishotdog
路
3Comments
converge
路
3Comments
neomh
路
3Comments
CharlesCCC
路
3Comments
wyvers
路
3Comments
Most helpful comment
This is important work, but I think Instagram will notice access from specific account to the graphQL DB.
This is not recommended since we want not to get blocked.
I think we shall maintain another account that crawl throw the DB using a proxy server and save all this db to be used from real accounts.
Best solution is to use MySQL server but a 'write - read' async mechanism can also be implemented easily.
I am working in it now it is working but need many improvements.