just bought followliker and wanted to know in the comment section does <username> still apply like it did with instaget
can this be done on instagram as well? if so, are there anymore variables like this we can use?
thanks.
Hello followliker,
I have many accounts running with the software and it is honestly awesome.
But, the account that i just made 30 minutes ago are all get MAccess failed, but are still working and another error.
Last response code: 403 -> ERROR: The requested URL could not be retrieved ERROR The requested URL could not be retrieved The following error was encountered while trying to ret... was received from instagram [Lily_KUALALUMPUR7]
why is this happening? I need this fixed asap. Reducing my daily income if it continues until tomorrow.
Is the autounlocking still working for Twitter? It worked when the feature first came out (before there was a button for it) but after the latest update it doesn't seem to autounlock anymore, and I have the option checked.
just bought followliker and wanted to know in the comment section does <username> still apply like it did with instaget
can this be done on instagram as well? if so, are there anymore variables like this we can use?
thanks.
Hi Weblues,
Can I ask for 2 feature requests please?
1) No matter how many pix we scrape, can you add a feature to only like/comment on 1 picture per 1 user only? I have tried setting this number to 1 but gave too many search inquery errors. Then lead to temporary banning. This has happened to more than 5 of my accounts.
This should also apply for FLC option too of course. In fact this is most important for FLC feature. If I set photo scrape number to only 1, imagine how long all the other tasks will take to be completed by end of day. I have already tried this many months and it doesn't work good.
So yes, no matter we have the photo scrape limit to 40, 50, 100 - should still scrape all in the beginning but should only scrape 1 picture per 1 user. Even better would be if you can just have option to choose however many picture per 1 user no matter what photo scrape limit.
2) For the "ignore private profile" - thank you for this feature but could you make it where FL will be scraping non-private profile in the beginning when it scrapes? Meaning right now, it determines if a profile is private or not as it scrapes along and this delays the whole following process.
Thank you so much Weblues, I am pretty sure i am not the only one with these featureq request so hopefully you can implement them.![]()
Hi Weblues,
Can I ask for 2 feature requests please?
1) No matter how many pix we scrape, can you add a feature to only like/comment on 1 picture per 1 user only? I have tried setting this number to 1 but gave too many search inquery errors. Then lead to temporary banning. This has happened to more than 5 of my accounts.
This should also apply for FLC option too of course. In fact this is most important for FLC feature. If I set photo scrape number to only 1, imagine how long all the other tasks will take to be completed by end of day. I have already tried this many months and it doesn't work good.
So yes, no matter we have the photo scrape limit to 40, 50, 100 - should still scrape all in the beginning but should only scrape 1 picture per 1 user. Even better would be if you can just have option to choose however many picture per 1 user no matter what photo scrape limit.
2) For the "ignore private profile" - thank you for this feature but could you make it where FL will be scraping non-private profile in the beginning when it scrapes? Meaning right now, it determines if a profile is private or not as it scrapes along and this delays the whole following process.
Thank you so much Weblues, I am pretty sure i am not the only one with these featureq request so hopefully you can implement them.![]()