hey coders, i had a bot made for me and to my knowledge it does bypass the api (it can scrape thousands of photos per min) and like thousands of pics per min but the danger with that is that your account can get rated or flagged so i never set it at full capacity
anyway, i set my bot to do about couple hundred likes per minute and it was doing just fine for about 2 weeks, but today it started acting weird. it would like about 5 pictures and then it would stop. the error message i got from my bot was that it had hit a limit. basically it was getting limited after only a couple likes.
as u all know the reason why liking thru 3rd apis parties suck is because there is a limit. now it seems like my bot is hitting a limit even though its not using any third party apis, but as of today instagram has made some kind of change which is causing my likes to get limited.
to my knoweldge i have the best type of bot available, but maybe im wrong
is there a way in which you can do likes without hitting a limit ? pls know that my bot was able to do this for 2 weeks straight and all of that came to a stop today. even so, I know there must be some way to get around this new change instagram has implemented.
any of you coding geniuses out there know of an alternative or possible methods to explore in getting around the limit?
Aug 23, 2012 12:33 AM
(This post was last modified: Aug 23, 2012 12:33 AM by marvinn.)
Hmm, what are you using? A Webborser?
Edit: 1000th posts today haha yay :)
![[Image: HJdK32K_x]](https://lensert.com/HJdK32K_x)
lensert.com is the new screenshot utility, try it out now!
OSX & WINDOWS
congratz marvinn, and yes, need more info if you made the bot, you didn't tell us how your doing it, the headers/cookies may have changed, does it work at all or just limited? they could have started limiting by IP, do you use proxys? a single account? information plz.
(Aug 23, 2012 12:46 AM).Dangerous. Wrote: congratz marvinn, and yes, need more info if you made the bot, you didn't tell us how your doing it, the headers/cookies may have changed, does it work at all or just limited? they could have started limiting by IP, do you use proxys? a single account? information plz.
it still scrapes and it will like the first round of pics (about 3-5) and then when it tries to go for 2nd round it is unable to do so because of the limit.
its not by IP because ive tried it with various proxies and all yield same findings
i even went a step further and tried it with a combo of different accounts and different proxies. and still same error.
yes it is a single account
strangely i have a friend who also encountred a similar problem. his bot (which also bypasses api to scrape.like photos) stopped working last week though ...it worked fine for about 2 months but last week his likes stopped working & it gave him this error
"{"status":"fail","message":"Please update your Instagram app to continue liking photos"}" he updated his app and the error still remains
NOTE: that is what his error message says. i think mine is different issue because his stopped working last week, while mine just stopped working today.
if instagram made a site wide change why would it affect his last week while mine ran perfectly for that entire duration and only stopped working today? perhaps related issue ?
im suspecting it has something to do with instagram modifying the header request ...
wondering if anybody else on here has heard of or encountered a similar problem ?
well apparently instagram updated 6 days ago to what they call 3.0.
so you didn't tell us if your using webbrowser control etc. you may just need to get the plugin LIVE HEADERS for firefox and take a looksey. ^.^
http://help.instagram.com/customer/porta...request%22
Yeah my instagramm bot give me exact the same error. I know that the encryption of signed_body has changed. I am on it. ne new signed Body looks like SHA256. Perhaps i will find a way.
(Aug 23, 2012 01:51 AM).Dangerous. Wrote: well apparently instagram updated 6 days ago to what they call 3.0.
so you didn't tell us if your using webbrowser control etc. you may just need to get the plugin LIVE HEADERS for firefox and take a looksey. ^.^
http://help.instagram.com/customer/porta...request%22
i would have an "ah-hah!" moment if the bot stopped working 6 days ago as soon as insta updated to 3.0 then i could say yeah thats probably the reason, but considering that the bot has been working for past 2 weeks (including last 6 days) im kind of stumped.
i didnt code the bot and ill ask my coder about this, but when you say "web browser" control. do you mean is the bot using firefox ? i dont think the bot is using any web browser.
i used to have a UBOT that for sure used a web browser because i could see it in the bot's window., but this bot doesnt look like it uses a web browser?
(Aug 23, 2012 02:05 AM)geldformeln Wrote: Yeah my instagramm bot give me exact the same error. I know that the encryption of signed_body has changed. I am on it. ne new signed Body looks like SHA256. Perhaps i will find a way.
how long have you been having this problem?
DO NOT DEAL WITH THIS MEMBER
Aug 23, 2012 01:36 PM
(This post was last modified: Aug 23, 2012 01:37 PM by facebookdoom.)
(Aug 23, 2012 12:51 PM)bobsleds Wrote: i would have an "ah-hah!" moment if the bot stopped working 6 days ago as soon as insta updated to 3.0 then i could say yeah thats probably the reason, but considering that the bot has been working for past 2 weeks (including last 6 days) im kind of stumped.
i didnt code the bot and ill ask my coder about this, but when you say "web browser" control. do you mean is the bot using firefox ? i dont think the bot is using any web browser.
i used to have a UBOT that for sure used a web browser because i could see it in the bot's window., but this bot doesnt look like it uses a web browser?
how long have you been having this problem?
Well your coder could have been using an external site to automate instagram such as statigr.am or web.statgram.com and those sites might have changed. If you want to verify, feel free to pm me the file and I'll take a look at it.
(Aug 23, 2012 01:51 AM).Dangerous. Wrote: well apparently instagram updated 6 days ago to what they call 3.0.
so you didn't tell us if your using webbrowser control etc. you may just need to get the plugin LIVE HEADERS for firefox and take a looksey. ^.^
http://help.instagram.com/customer/porta...request%22
You can't use Instagram directly in a browser.
(Aug 23, 2012 01:36 PM)facebookdoom Wrote: Well your coder could have been using an external site to automate instagram such as statigr.am or web.statgram.com and those sites might have changed. If you want to verify, feel free to pm me the file and I'll take a look at it.
i know for a fact he is not using statigram or webstagram to automate.
i do have a hypothesis of what happened. and i do think it has something to do with the instagram update.
i think the reason why some people's bots stopped working has to do with the day they updated the app.
which is why our bots didnt all stop working at the same time. some peoples bots stopped working 6 days ago while mine stopped working 1 day ago.
i updated my app early yesterday morning and a few hours later my bot stopped working.coincidence? maybe but its a hypothesis of mine that maybe my bot stopped working because i updated the app on my tester account and that some how instagram was able to disable the method in which the bot was liking pictures..
anyone? pls help if u have even a skeletal idea of how to fix this
Instagram need the signed_body sended in post content, that's the change, first u was able to send succeful create/destroy requests without the signed body, now not. Insta checks: method ( just post), UserAgent and signed_body, so u have only to generate it. That's the only way
(Aug 24, 2012 05:41 AM)nostuff Wrote: Instagram need the signed_body sended in post content, that's the change, first u was able to send succeful create/destroy requests without the signed body, now not. Insta checks: method ( just post), UserAgent and signed_body, so u have only to generate it. That's the only way
And how are you successfully generating the signed_body part of the POST data? Did you find the encryption key? If so... care to share some info? :)
Need a custom software? Check out my freelance service here! 6+ years and counting, never a complaint :)
STOP STEALING CODE.
FREE NATHAN
People who report posts are lamers.
(Aug 24, 2012 06:01 AM)idb. Wrote: And how are you successfully generating the signed_body part of the POST data? Did you find the encryption key? If so... care to share some info? :) blabla
I think the code is clear and no need an explain.
If anyone need help pm me.
I ve done a script who generates valid signed_body. Ask in pm.
(Aug 24, 2012 06:01 AM)idb. Wrote: And how are you successfully generating the signed_body part of the POST data? Did you find the encryption key? If so... care to share some info? :)
leave your skype in pm, I can not answer u as i havent 10 posts
another coder said:
"u only need the encryption key
for logging in via non api and creating accounts not for liking..."
can anybody finish the rest of this sentence?
what do we need to do then if we need to like photos???
Aug 24, 2012 11:46 AM
(This post was last modified: Aug 24, 2012 11:47 AM by idb..)
You DON'T need the encryption key for logging in through non api. You need the encryption key if you're using the "secret" api from the app. The documented API doesn't require any of that bullshit.
Need to just stop wasting time trying to get help from these guys who have it figured out because they are only talking people in circles trying to keep the shit a secret. Greedy bastards of the internet disgust me.
Need a custom software? Check out my freelance service here! 6+ years and counting, never a complaint :)
STOP STEALING CODE.
FREE NATHAN
People who report posts are lamers.
(Aug 24, 2012 06:19 AM)nostuff Wrote: blabla
I think the code is clear and no need an explain.
If anyone need help pm me.
I ve done a script who generates valid signed_body. Ask in pm.
leave your skype in pm, I can not answer u as i havent 10 posts
are you still working on the .so ?
pls update.
|
