-
Notifications
You must be signed in to change notification settings - Fork 7
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
Login required for locations as of 04/2022 #3
Comments
Hey man, this is an appreciation comment of how amazing this implementation is :D thank you very much i learned a lot! This repo is definitely underrated! |
Locations cannot be retrieved anymore without login. Hashtags as of 04/2022 still do work without login but seldomly in TOR (you must be lucky to hit a good endpoint), e.g.
but it might be only a matter of time until it's going to be closed entirely (without login). However, posts seem to be consistently publicly available (maybe even for a longer time to positive Instagram SEO). Hence, I propose
I described it here as well. |
Hashtags can still be mined (with enough patience, partially solves #3). Location sites however unfortunately not.
Works again for some reason, test e.g. here. Closing for now. |
After recent changes, the old endpoints, e.g.:
https://instagram.com/graphql/query/?query_hash=ac38b90f0f3981c42092016a37c59bf7&variables={"id":"<some_location_id>","first":50,"after":""}
seem not to work anymore.
However location IDs can still be mined successfully via a different endpoint:
Currently don't have time to investigate further but this quick fix works for me:
idata["data"]
withidata["graphql"]
.Same applies to hashtags. Just updated the code so hashtags can be mined again.
The text was updated successfully, but these errors were encountered: