Search results

Was coming back to post the link but you were faster. Thank for your comprehension @520am, appreciate.

Yeah sure, I got your point and I totally understand all of the angry customers. Trust me when I say I feel sad for the decisions I had to make these days. I'm probably not the best community manager and probably lack a great sense of communication - even though I started to write my blog entry...

I'm trying to finish to write down the announcement today and spread it around. If a moderator and/or admin wanna PM me cause they think I'm in a scamming position because I didn't wrote down any TOS protecting myself, let me know. When I first came here, I just wanted to share the tool I...

Hi there. I'm coming up with explanations on what happened with Automagram - we got shutdown, I hope you guess I didn't want to stop the service. It's not easy to control the badbuzz, and to put it in a nutshell, no, I won't be able to refund every single person (not that I don't want). "Sell...

Yeah guys, I didn't vanished, just preparing a detailed blog entry about my experience with Automagram. I'm almost done with it, will publish and spread the word soon. Hard to manage the "bad buzz" effect as I was naive enough not to loose time on TOS and thought everybody was aware that it...

Don't remember how long they were blocked, but yeah it's something like a week.

It worked for me too when I moved to a new IP, new client etc. But just when I was the only one to use the bot; when I re-opened to other users, got ban within 10 minutes.

Well, I changed IP, setup a new Instagram client on a new Instagram account and it was working. Got the following error again right after I redirected all the traffic from the old IP to the new IP (probably more than 1000 requests / minutes instant on a newly created Instagram client, that's...

Yeah, So I tried to change my client id and client secret used by my webapp by creating a new client (but keeping the same domain and URIs for the address/callback) but it then throws: {"meta":{"error_type":"APIError","code":400,"error_message":"We've taken extra measures to protect the...

Yeah, I think I'll need to change my client, don't know yet as everything's working great on my dev env. Maybe it's my client sending out too much like (100k every two hours) so it got blacklisted on the likes, I don't really know. I'll keep you guys posted.

Just FYI. all, we're currently facing an issue with the Instagram API sending us errors 400 when trying to send out likes. We're trying to analyze and find a workaround if there's any. @IXIVMMVII - You can contact me by MP if you want, am on a rush right now but I'll be pleased to answer your...

Got the same with Instagram API, massive Error 400, ApiNotAllowed / Cannot like this media. Anyone?

All my blocked clients has been unlocked without requiring any actions from them. I started delivering again without any issues for now.

Just FYI. guys, one of the client I blocked the follow button to got his button unlocked. He didn't told me tho' if he contacted Instagram or not. Still, he got all the followers I sent before stopping the process added to his counter. Check the screenshot from before delivery (then he got...

Do you guys know about Automagram? Still in development but you can use it for free and choose to pay or not for extras.

Just to follow-up, automatic execution should now be working fine again. Here's the last summary mail I received after the job was done for the last execution. Should be executed every 2 hours from now on.

I recently added this icon. It's not activated yet cause I'm still working on the page behind but it'll lead to a detail page where you can live edit the recipe and see the execution logs of the recipe; this way you'll be able to have a log and see when you ran the recipe manually or when we ran...

I recently changed the cron jobs taking care of this; am gonna check and follow-up here and on Twitter when it's back to normal. - Edit: Error found, everything should be working from now on, execution on a 2 hour basis. - Edit2: Error found and fixed but it seems my cron isn't running. Checking...

Still looking forward for a known solution/delay.

Damn... looks like there's a crackdown going on.