I've been considering the merits of setting up some tinder bots for the usual cam-site referral link routine. I'm curious to hear whether I need to take any further measures to ensure my bots stick around long enough to earn back the handful of dollars I spend on their virtual phone numbers. The Plan Set up a Twilio account with a prepaid card to generate phone numbers. $1 / Month per phone number isn't bad. Set up an android emu so I can register for a new tinder account using my VPN. Sleeping with tinder girls is my only hobby, so I don't want to get my home IP blocked. Use the cleverbot API to simulate a more authentic conversation than your run of the mill tinder spam account. After 3 - 6 messages hit the mark with the twilio phone number I used to create the account. Keep the cleverbot conversation running for maybe 2 - 5 more messages, then hit the dude with a "wanna know a secret... I'm actually a cam model." hook. Obviously any unsolicited, unsavory images would be deleted, the profile unmatched, and the phone number would be scrubbed from my records. Protective Measures I've been reading up on some statistics regarding how often women check their phones, how often they swipe right, when users are most active, how quickly they typically reply, etc. so that I can make my bots act as realistic as possible. The bot will message a fraction of matches first, and will ignore up to another X% of its matches, so long as it engages with at least 70% of its matches within two days of matching. I don't have access to a botnet to ensure that every profile is associated with a unique home IP address. My goal with this project is to try using a large volume of high quality bots to keep the profiles online for longer, even if they may not individually realize the same returns as a bot that takes a more aggressive "like and message everyone" blitzkrieg approach. Some Questions 1. Am I likely to have issues sending and receiving messages using VPNs and proxies? I would think that blocking VPNs / proxies would make sense for a company whose product runs almost exclusively on mobile devices which are hardly ever configured to use either. Unfortunately, if I don't use any proxies then I've got a relatively slim number of IP addresses to work with. I want to be able to keep this project rolling long term. 2. Do you think that Tinder is smart enough to check a user's IP address against their location? If I'm restricted to locations I can find proxies for, I'm going to miss out on a decent chunk of the market. The app is a fucking trainwreck, of course, so I don't expect this to be an issue. 3. How many profiles do you think I can safely run off of a single IP address? I would expect that if a hundred profiles running off the same IP address get reported as spam, that IP would eventually get blocked. Likewise, too many profiles on one IP address would presumably raise a red flag if their engineers know what they're doing. I'm sure colleges, busy coffee shops, convention centers, etc. can all see between 5 and 50 active users on one public IP address so there has to be some leeway, but I'm curious if anyone has firsthand experience regarding a good upper bound to profiles / IP address. 4. Should I be concerned about Tinder checking for existing photos / checking for similar biographies? This seems like a huge waste of computational resources to me, but I figure it's worth asking. Ideally, I'd like to hit all of my target regions with each profile that I compile to minimize the amount of time I have to send digging up pictures and finding new ways to say "I love to eat, love, and laugh. Hanging out with my besties is my fav!"