CodingAndStuff
Regular Member
- May 6, 2012
- 239
- 92
I've gotten lots of messages recently about people not being able to create accounts now - specifically those who are follower/like providers. I've already reversed the entire application and got a working solution to create accounts and do all of the standard tasks as well as the analytics.
I'm at a bit of an impasse here, though. I know that the community in general would benefit from a particular portion of my codebase (if you've looked at the internal functionality of the application recently, you'll know exactly what I'm talking about - hint: qs_stamp). Without this particular functionality, your private api-based bots are useless. Eventually Instagram will implement the functionality into the login requests instead of just the account creation one. I also don't want to saturate the market and have Instagram flooded with spammers.
See the dilemma? I'm stuck between watching everyone crash and burn and ruining Instagram for everybody.
My potential course of action is currently split between the following:
1. Do nothing and silently profit from Instagram and laugh at everyone else using ubot-based applications.
2. Create quality (US) PVA accounts and sell them for a profit, helping the community in the process (Don't really want to do this tbh)
3. Opening up my own API to allow developers access to the qs_stamp generation portion of the codebase, allowing them to create accounts.
4. Integrating my system with a preexisting web-based bot (would probably go with igerslike to be honest), and allowing people to use that
I suppose the purpose of this post is to pick the brains of my fellow developers and see if there is a general need for this service. What say ye, my brethren? Keep it private or open it up as a paid service?
I'm at a bit of an impasse here, though. I know that the community in general would benefit from a particular portion of my codebase (if you've looked at the internal functionality of the application recently, you'll know exactly what I'm talking about - hint: qs_stamp). Without this particular functionality, your private api-based bots are useless. Eventually Instagram will implement the functionality into the login requests instead of just the account creation one. I also don't want to saturate the market and have Instagram flooded with spammers.
See the dilemma? I'm stuck between watching everyone crash and burn and ruining Instagram for everybody.
My potential course of action is currently split between the following:
1. Do nothing and silently profit from Instagram and laugh at everyone else using ubot-based applications.
2. Create quality (US) PVA accounts and sell them for a profit, helping the community in the process (Don't really want to do this tbh)
3. Opening up my own API to allow developers access to the qs_stamp generation portion of the codebase, allowing them to create accounts.
4. Integrating my system with a preexisting web-based bot (would probably go with igerslike to be honest), and allowing people to use that
I suppose the purpose of this post is to pick the brains of my fellow developers and see if there is a general need for this service. What say ye, my brethren? Keep it private or open it up as a paid service?
can be a disaster. It will break down instagram and will definitely allow EVERYONE to create new accounts or at least flood with empty ones. I think you should create an API and make it available for a price so only serious people buy that stuff. Though, I was reverse engineering the same thing a few days back, have only seen the java code for qs_stamp, any pointers as to what it is concerned with?