How to Retweet All New Of ACCOUNT but IGNORE the replies

[bitcoin]

Martin,

I just noticed (I'm a bit slow sometimes) that Retweet All New Of doesn't ignore replies. How would I use TD to solve the following customer request:
Can you retweet me 3 times per day, in 8 hours intervals, one tweet at a time?
Preferably: do not retweet replies ++ do not retweet retweets

Let me know please :)

[martin@rootjazz]

retweet tab does have that option I believe (either main tab / filter)

then custom search get latest repeat every 8

[bitcoin]

retweet tab does have that option I believe (either main tab / filter)

then custom search get latest repeat every 8

It took me a while, but found it: viewtopic.php?f=30&t=1545&p=30410&hilit ... nly#p30410

If I only retweet 1 item every 8 hours, I don't have any randomization, right? (I've enabled the option Stop search if find previously processed item).

I 'want' the randomization because I want to reach as many ppl as possible, and not be stuck at 1 single time slot (as you know, I like large randomizations).



I'll be testing above statements by adding a random delay (in seconds), maybe the Action (despite being told only to process 1 tweet at a time) ads this random pause before the next execution +8 hours later...?

[bitcoin]

Update: random delay doesn't work here.

SO: Feature request pretty please: can we have a Random interval option for "Retweet"-tab?

[martin@rootjazz]

I believe if you RIGHT CLICK > EDIT DB after creation you can expose a repeat after X fluctuation parameter

[bitcoin]

I believe if you RIGHT CLICK > EDIT DB after creation you can expose a repeat after X fluctuation parameter

This parameter, right?

Code: Select all

FluctuateRepeatEveryXMins:0

If I have

Code: Select all

NumMax:1
RepeatEveryXHours:0
NumRepeatsTodo:0
RepeatEveryXMins:360

Setting FluctuateRepeatEveryXMins to :19 would add a randomization of 0 - 19 minutes to the 6 hour cycle? (6 hours = 360 minutes)

[martin@rootjazz]

It would make your potential repeatXMins value:

341 - 379

360+-19



Regards,
Martin

[bitcoin]

It would make your potential repeatXMins value:

341 - 379

360+-19



Regards,
Martin

Oooh ok, I always thought the (-) here was incorrect. The Action is set to run at time xx:yy. Only then it can decide its randomization. And the randomization cannot let the action start 19 minutes before it starts.

[martin@rootjazz]

errr no I don't think so, it "should" be +- the fluct value



so repeat: 100

fluct: 10
repeat: 90-110

[bitcoin]

errr no I don't think so, it "should" be +- the fluct value



so repeat: 100

fluct: 10
repeat: 90-110

For amount of times, yes. But for time periods...? You have to set a fixed time for the action to start (schedule). So once it is started, it can only do the "+" randomization. Going back in time with "-" looks tough, no? : )