Block feature adjustments

[martin@rootjazz]

working fine here, scraping your followers with a min active date.

One thing, as the scrape returns MOST RECENT followers they are most likely active, you would probably do better, scraping all followers first to a list, reversing the list, then testing them for inactive.

But I will leave the scrape running to see if I can trigger the COMPLETE EARLY event I can see in your logs, but so far (10+minutes it hasn't happened)

[martin@rootjazz]

still running fine:

Days since last tweet: coy_placido: 7
* FAILED check active: lastActive: 100 > 7 < 0
* IGNORE: active date
* IGNORE: Filtered: https://mobile.twitter.com/coy_placido
Filter check: https://mobile.twitter.com/LowkystSwarm
Checking Filter: Ignore Verified
Filter user: https://mobile.twitter.com/LowkystSwarm : LowkystSwarm
Checking Filter: LastActive
Check Last active: 100:0

up to users last active day 7 as go through older followers...

[martin@rootjazz]

been running fine all day. Am going to stop the process now. Whatever happened for you, is not happening here.

Are you on the latest version?
https://rootjazz.com/twitterdub/updatetesting.html

If not, try that, if you are, when I get a new build out I'll let you know as maybe there have been changes I cannot remember that are having an effect (although I cannot think of any)


Regards,
Martin

[Bri]

I'm always on the new version 3.112 17/04/2020 64bit

it must be my account (DB), if you remember, I had problems in the past with the database. the size was small when I exported the account with data (even when this is the account that has done most process jobs in the bot), to fix this I merged all the follows, likes, rts, etc, and it then made my export account database file larger, as originally it was in the KBs range, not MBs.

I don't understand how it works for you but not me, I'll have another go, did you already tell me that you found out why it completed early?

thanks, bro x

ps, are my screenshots ok? did I do it right, use left numbers to find inactives?

[Bri]

working fine here, scraping your followers with a min active date.

Please send me a screenshot of what you did to make it work. blank out my username though if you post it publicly lol

[martin@rootjazz]

working fine here, scraping your followers with a min active date.

Please send me a screenshot of what you did to make it work. blank out my username though if you post it publicly lol

SCRAPE tab
enter your profile url
custom search > followers
Filter: min days active: 100
Run the search

That was it. The issue for you is the COMPLETE EARLY event. I don't know why it occurred, nor could I replicate. That is the issue, trying to figure that out. But as above, I'll get a new build ready soon, so you can be testing the same codebase as me. As you said, if we do the same, we should get the same results....

[Bri]

Thank you so much, I really appreciate your time and support

[Bri]

Can you add some more info to the logs, please

this is an example of a log from a follow process. it shows you how many items have been done, in the current process, and over 24 hours.
it would be great if this info could be available in the stats tab too

22:47:38: Loading previous db logs: ee04962b-a073-4141-825a-8b000e56a58a_Follow
22:47:40: Loaded previous db logs: 344720 processed: 2417 within 24hrs: 47

[martin@rootjazz]

isn't there already a 24 hours / daily read out? I thought that there was

[Bri]

No bud. Hence me asking,

There is a current one. But if the process starts again, the number resets for the current process

Thank you for your time. You are amazing