fa
Feedback
Evelode

Evelode

رفتن به کانال در Telegram
548
مشترکین
اطلاعاتی وجود ندارد24 ساعت
اطلاعاتی وجود ندارد7 روز
اطلاعاتی وجود ندارد30 روز
آرشیو پست ها
Repost from N/a
Important change for all users. Async algorithm is dangerous because it’s too fast for story like and masslooking. It's also
Important change for all users. Async algorithm is dangerous because it’s too fast for story like and masslooking. It's also can eat all your server RAM. Please avoid usage of that feature. I uploaded a fix to disable it for all tasks by default. Please apply that changes and restart your tasks. https://github.com/nextpost-tech/reactions/commits/main

Great app to test any proxy on phone as VPN profile. Very easy to use. https://apps.apple.com/ru/app/potatso/id1239860606

Please don’t use async feature if you are having throttled exception for story like action. This feature should be used with
Please don’t use async feature if you are having throttled exception for story like action. This feature should be used with caution because it’s can increase frequency of likes per hour what can be a reason of exception 429 (Throttled).

DigitalOcean - Our trusted provider! Deploy faster & scale easier with an application server VPS/VDS (droplet) that saves your team time & money. From $6/mo for droplet with 1GB of CPU, 25 GB of SSD Disk and 1TB of transfer. https://m.do.co/c/502c5061cba5

You should pay attention that current synchronous algorithm is more safe by default. Asynchronous algorithm should be used carefully.

If you are using Asynchronous Settings this is new recommended values. Higher values can trigger throttled exception (code 42
If you are using Asynchronous Settings this is new recommended values. Higher values can trigger throttled exception (code 429) too many API requests. Anyway this feature is experimental. Please use with caution. For this setup I use following settings: - Delay for like stories (10) - Delay for stories masslooking (10) - Batch size for masslooking (10)

Fix for slow loading of Nextpost This is a fix for slow loading of Nextpost that can happen from time to time. We found that Nextpost core function named as ipinfo() (added not by us, it used by origin Nextpost developer) can cause 504 (Gateway Timeout) response because it’s use plain file_get_contents() function which have no user agent and use a huge timeout value by default. 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.

Attention! Function Like highlighted stories is not recommended for usage. It’s downcrease the speed and very risky for your
Attention! Function Like highlighted stories is not recommended for usage. It’s downcrease the speed and very risky for your accounts. This function will be completely removed in new version. Please avoid usage of this feature.

An important thing about why actions speed can be slow When your targeting reach is small you may see that after a week you a
An important thing about why actions speed can be slow When your targeting reach is small you may see that after a week you actions speed is dropped a lot. That’s not an issue. This is how double action prevention algorithm works. You have 2 ways to fix it: - Set interaction frequency to 1 day, by default it’s 30 days and this is pretty high - Fully update your targets

Is the Threads app dead?
Anonymous voting

What do you think about Threads automation?

Is Threads are dead app?
Anonymous voting

By the way you already can use new function to detect gender by name. https://github.com/nextpost-tech/reactions/commits/main
By the way you already can use new function to detect gender by name. https://github.com/nextpost-tech/reactions/commits/main

Reactions Pro module version 15.0 will be released on the next week. There will be 8 new targeting types, new module updates
Reactions Pro module version 15.0 will be released on the next week. There will be 8 new targeting types, new module updates system, some requested features and maybe some of new actions.

This is very important change. After a lot of time spent on debugging I finally detected what cause freeze of activity.

🤯 Critical freeze issue detected and fixed in Reactions Pro module. https://github.com/nextpost-tech/reactions
🤯 Critical freeze issue detected and fixed in Reactions Pro module. https://github.com/nextpost-tech/reactions