Permanently Closed Marketplace Sales Thread

Status
Not open for further replies.
I'm struggling to understand how you calculated the number of accounts per profile with that setting cause I think only 1 account can comprehend such a large number of retweets.

Edit: I meant that lets say you have 24 accounts per profile how can you have at least 1 retweet per account without the bot fetching at least 24 hours activity. Wouldn't be more logical between 7-8: 24h?

I am having a hard time trying to understand what you mean and what it is that you are trying to accomplish.
 
Ok here
1. Run every 60-60 between 7-8
2. Run every 60-60 between 8-9

You say: run between 7-8 and retweet all the tweets between 7-8 from an account. I say run between 7-8 and retweet all the tweets from the last 24 hrs. Which one is more helpful?
 
Ok here


You say: run between 7-8 and retweet all the tweets between 7-8 from an account. I say run between 7-8 and retweet all the tweets from the last 24 hrs. Which one is more helpful?

I never said anything about only retweeting tweet's from a specific time-range I only suggested how to run your schedules. By between 7-8 I mean between 7pm and 8pm. It is not possible to only retweet from certain time-range with the Retweet Search from:username. It is possible with the Retweet User however not when you use the 'between' option, as I explained how and why that task works earlier.

I'm not even sure why you would want to retweet so many tweets from the last 24 hours at a specific time of day anyway, but up to you.
 
I never said anything about only retweeting tweet's from a specific time-range I only suggested how to run your schedules. By between 7-8 I mean between 7pm and 8pm. It is not possible to only retweet from certain time-range with the Retweet Search from:username. It is possible with the Retweet User however not when you use the 'between' option, as I explained how and why that task works earlier.

I'm not even sure why you would want to retweet so many tweets from the last 24 hours at a specific time of day anyway, but up to you.

I don't want to use search from:username because I want to avoid creating loops. By trying to tweet at a specific time I try to avoid running more Schedules at the very same time and if that could be avoided by any other way that would be great.
 
I don't want to use search from:username because I want to avoid creating loops. By trying to tweet at a specific time I try to avoid running more Schedules at the very same time and if that could be avoided by any other way that would be great.

The retweet user will only retweet new tweets since the last time the schedule ran (the lower minute). You can retweet user on something like a 120-120 minutes schedule however if you use the between time it will obviously miss alot of tweets that fall inside the times it doesn't run.

If you have multiple schedules and want to avoid them running at the same time, you set them to run at different intervals i.e. one every 120-120 and another every 115-115.

The last update included updates that prevent loops, so you can try using from:username with whichever settings that suit your specific needs.
 
having issues with retweets also, no matter what times i set it for it wont find the tweets i post, i delete the tweet repost it and start the retweet campaign again and same thing happends its not retweeting correctly
 
having issues with retweets also, no matter what times i set it for it wont find the tweets i post, i delete the tweet repost it and start the retweet campaign again and same thing happends its not retweeting correctly

Tweets take a few minutes to show up in search. You can see for yourself by searching from:yourname at https://twitter.com/search-home

Try create a Retweet User, set it to run every 60-60, target your username and set it to 100%. Now wait 5 minutes and press Run Now.
 
I've been getting a problem when trying to Scrape using the Search function.
I need to scrape 71 tweets, but when the process begins the acc only scrapes the first 21 tweets and freezes.
Here's the screenshot of the bug in the History tab: http://imgur.com/kj3CLIM
Note: My account is PVA.
Thanks
 
I've been getting a problem when trying to Scrape using the Search function.
I need to scrape 71 tweets, but when the process begins the acc only scrapes the first 21 tweets and freezes.
Here's the screenshot of the bug in the History tab: http://imgur.com/kj3CLIM
Note: My account is PVA.
Thanks

Should be working after updating
 
i thought all fields were spinnable.

i setup a scheduled 'follow users followers' with a spin list and it breaks.

when I looked at saved sced, I see {name1--name2} when I entered {name1|name2}
 
i thought all fields were spinnable.

i setup a scheduled 'follow users followers' with a spin list and it breaks.

when I looked at saved sced, I see {name1--name2} when I entered {name1|name2}

Almost all.

Users following/followers does not in this current version however I will add to the todo list for a future update.
 
Can anyone tell me how the current version performs? I saw some complaints about the beta version but now that over a year has passed, can anyone couch for it now?
 
Can anyone tell me how the current version performs? I saw some complaints about the beta version but now that over a year has passed, can anyone couch for it now?

It has a trial so you are free to see for yourself
 
Version 1.63
Unfollow: Filters
 
has anyone got a txt file with lot's of bio's? I can't be bother to write or spin any... :p
 
yeh I saw that but I need bulk ones. I have to copy and paste those ones one at a time :sad:
 
Status
Not open for further replies.
Back
Top