I redownloaded the scripts from the front, page, but i'm pretty sure they are the same as the second download i did earlier in the day, when you updated it. Still having the same issues today, though i was hoping that leaving it overnight might fix things. It's a shame because that was a delicious script. Nice work anyway.
They are not the same scripts, they have longer wait times. When I come back home I'll re-test and do some adjustments to get them down correctly, I'll let you know in my next post/edit of this post.
Scripts don't working for me, I guess I should set facebook and twitter's language to English right?
Yes - it needs to be in English. I've also had a user of my scripts have a complete issue with using it with Google Chrome, but worked fine for Firefox - so if it doesn't work good with one, try another browser. But obviously make sure you download iMacros on it.
Thanks a lot for the share first of all. I am trying retweets iim version. It works fine. But I have a question. As far as understood it retweets 5 times. As far as I know you can RT 50 tweets per hour. Is there any changes with new Twitter API - rate limits? So if its 50 per hour can i use loop 10 times? Also looks like waiting time for all 5 RT is 4 seconds?
Second, I've found this code which will randomize waiting time between retweets to prevent bot detection and ban:
SET !VAR1 EVAL("var randomNumber=Math.floor(Math.random()*10 + 1); randomNumber;")
WAIT SECONDS={{!VAR1}}
But I confused to what parts of your script to add it, should it be 5 times or 1 time in the beginning? Could you advise please
I think you're overthinking it. If you've hit your limit, you shouldn't be notified. To my knowledge - I don't believe there is even that many people that are using RT on AMF, but that could have also been another category, I don't remember.
I don't think random waits is necessary, Twitter doesn't have a massive algorithm to detect for scripts or bots, it's not like they have some anti-automation software that is built into it.
Since it's uneeded, I will not implement it, however if you are willing to do it...you would add the SET VAR1 line at the top of the script, underneath the SET! ERRORIGNORE and above the start of the script, then add your WAIT SECONDS={{!VAR!}} anywhere you want a random wait time. But it seems that your wait time is from 1 - 10, but 1 is way too short of a wait period. Perhaps you could make it 3 - 12 or something like that, because 3 would be the bare minimum - otherwise they'll notify you that you closed it out too fast.
