-
Notifications
You must be signed in to change notification settings - Fork 30
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
New feature request: Navigate new Explore page for web version. #92
Comments
Yeah, this is a critical change IG recently made. And it would fail the flow.. |
+1, it would be great |
This is the path that allows infinite posts:
|
@shine-jayakumar was that URL implemented? I can see it in the code but I don't know which parameter to use. I am trying to like posts of a tag or location. |
|
@shine-jayakumar It works for me and it has infinite scroll: https://www.instagram.com/explore/search/keyword/?q=rock%20climber |
@ap0l0 Interesting. It doesn't seem to work for me. I tried a different account too. Some region restriction? |
Interesting, did you try with another keyword? or try going to https://www.instagram.com/explore/search/ to see what loeads, and which keywords at the top That function has infinite scroll |
@shine-jayakumar does it work when you get keywords from your account? I tried with two other accounts and it seems to work |
same here, when I run a script it only finds accounts it doesn't find the new search explore page |
Opened a discussion regarding this: Navigate new Explore page for web version #98 |
When using the hashtag utility, IG now only posts the top 12-13 tags on the web version of the Explore Page. However, they have added a new Explore Page where the hashtag isn't used. For instance, #Denver displays only 12 posts out of over 14,000,000, but Denver works like the old Explore page where you can keep moving through them. Can we get a new function that allows the bot to navigate through that page as opposed to the hashtag page? Or in conjunction with it?
The text was updated successfully, but these errors were encountered: