Evelode

Product Latest IG API files for PHP + Update Instruction updated to version 7.0.67 IMPORTANT FIX: Timezone detection cause Nextpost slow load. Repository | Changelog | Buy Now This product is distributed throw a private GitHub repository, you need to buy a license key and join the repository.

Q: How to get list of users unfollowed by Reactions Pro module with unfollow function? A: In cases when something goes wrong and module unfollowed users you don't want to unfollow. 1. Login to redis cli: redis-cli 2. Auth with your password: 127.0.0.1:6379> auth your-redis-password 3. Find user ID's module unfollowed: 127.0.0.1:6379> KEYS *your_account_instagram_id-*-unfollow* For example: 127.0.0.1:6379> KEYS *11223344-*-unfollow* 1) "11223344-123948993-unfollow" 2) "11223344-374857443-unfollow" 3) "11223344-578493759-unfollow" ...

If you already apply changes to /app/core/App.php, you can skip that.

My fix for that.

Fix for slow loading of Nextpost This is a fix for slow loading of Nextpost that can happen from time to time. I found that Nextpost core function named as ipinfo() (added not by us, it used by origin Nextpost developer) can so much slow down Nextpost page loading speed. To fix that I added a Guzzle support with necessary useragent and lower timeouts. File location: /app/core/App.php My file with fixes attached to this message.

Product Latest IG API files for PHP + Update Instruction updated to version 7.0.66 NEW: Instagram iOS v.311 + Update for Account Center login Repository | Changelog | Buy Now This product is distributed throw a private GitHub repository, you need to buy a license key and join the repository.

Quick fix, thanks to @Jeff_new! 👍 If you encounter this error upon login: "We couldn't find an account with that username X. Please check the username you entered and try again." Solution: - Change your password. - Perform a clean login (make sure to uncheck the "Use current Instagram session settings" checkbox in the Platform section of the login page).

Important fixes for algorithm uploaded to repository of Reactions Pro module. https://github.com/nextpost-tech/reactions/commits/main

If you missed this... This is how new Reactions Pro module algorithms works: - 1:1 - like and view story only together, at a time - 1:1 + M - like and view story only together like in 1:1 + you will be able to continue doing masslooking (mass story view) when story like limit will be reached - Basic - mark stories as seen vary on batch size (we can mark as seen N stories per request, by default it's 10), after that do a story like (we can do only 1 per API request), actions works separately, that's mean if story like will be limited, you will be able to continue to do massloooking, and if massloooking will be limited, you will be able to continue to do story likes. - Advanced - the same as Basic, but with activity pause between story likes actions, in Basic we simply skip story like action if delay is not passed (will help perfom other mass actions faster) In conclusion: I think 1:1 and 1:1 + M better for now. And 1:1 + M is best choice for users who want to use masslooking (mass story view) without story likes also. The negative part of Basic and Advanced algorithms is possible timings resynchronization that can cause situations when you will mark as seen and like different stories (not the same stories) like in 1+1 or 1+1 + M algorithms.

New 1:1 + M algorithm uploaded to repository of Reactions Pro module. It's the same as algorithm 1:1, but you will be able to continue doing masslooking after story like limit reached. 1:1 algorithm - only works together with masslooking action, using this algorithm type you will like and view story only together, separate like or view will be not allowed. https://github.com/nextpost-tech/reactions/commits/main

Important fixes for algorithm uploaded to repository of Reactions Pro module. https://github.com/nextpost-tech/reactions/commits/main

This 1:1 algorithm only works together with masslooking action, using this algorithm type you will like and view story only together, separate like or view will be not allowed.

You can select it in Story Actions -> Like stories.

New algorithm for Reactions Pro uploaded to our repository. https://github.com/nextpost-tech/reactions/commits/main

🛍🛍🛍🛍🛍🛍🛍🛍🛍🛍 Black Friday started! 33% on all items! Only 7 days!  We just giving you a heads up, so you don’t miss out our biggest sale of the year. All Access Pass → Monthly subscription (250 active tasks): $80.39 (before $119.99) → Yearly subscription (250 active tasks): $669.99 (before $999.99) → All other plans are also with 33% off (our offer valid only for 7 days) https://nextpost.tech

This functionality of Proxy Manager Pro module can help you increase the trust score of emulation. If you use mobile proxies based on android devices, you can use your real phone device ID and custom user agent. By default we use random devices IDs because we don’t have real devices IDs, it’s something unique you need to have.

Delay for function getLikers() Usage: this function used to process post ID and get post likers list. For verified profiles this function is limited to 1 requests per post, that's mean you are not able to load list of all likers for verified profiles. Non verified profiles are not affected by this change yet. It's new Instagram limit for all accounts with blue badge. Delay for function getReelsMediaFeed() Usage: this function used to process user IDs list to get user stories list. The same way it's working when you load your IG app and see multiple stories if users you follow.

Please remember that whenever you see "Throttled Exception" it is caused by excessive use of some function in the API. This error is equivalent to error 429 (too many API requests). And most often this is solved by increasing delays, and we only have two (critical) delays, which are very sensitive and can cause such a problem. To fix this issue you need to increase the following delays and wait when limit of affected accounts will expire: - Delay for function getLikers() - Delay for function getReelsMediaFeed()