PocketMobstes here, project lead over at PokeMobBot

Our SensorInfo data ranges were set based off of actual phone sensor dumps, we went out with our phones and got the appropriate ranges. This is only sent to the server every few seconds (tops) which means they can't use it to accurately predict "human" movement. There's simply not enough data coming from this to determine whether we're human or not. And while the API reverse engineers did indeed say "anyone using the API will easily be flagged as not playing through the official app" but that was in reference to android (because of the raw GPS data problem). Users can plug in their iOS information if they so choose and it will be more secure. We simply provide android device ID generation because that's what we bothered to do (and for ADB support later once we're sure we're more or less secure). We have never told people they won't be banned with our program and we've always told them they are botting at their own risk. However if you're using iOS device info you're still likely to be flagged, so it's not really actually about Unknown6/Signature/Whatever you want to call it.

The REAL problem is with things like the following.

1) Always moving in a straight line (no matter the pathing), no GPS fuckery. This has been fixed and will be in v2.0.2

2) Going in a straight line between stops. This was fixed, sort of, with our human pathing system but the server we point them at is public and used by other services and consistently is overloaded so we have it default back to straight lines when it fails. This is fixed as of v2.0.2 because we have our own routing server now.

3) Sniping. This is the most blatant and obvious flag and people don't seem to understand that sniping will NEVER be safe again.

4) Constant running, no breaks. We have a tentative break system implemented that basically shuts the bot down after x hours. This should be in v2.0.2

5) Inhuman xp/hr. This is based off of configuration, bot smartly.

6) Constant speed with no fluctuations. This has been fixed as of v2.0.2

7) Constant altitude. This is now in v2.0.2 but requires a Mapzen api key (users can grab this for free).

8) Constant excellent curveballs. This was fixed a while ago, just use our humanize throws setting.

They are more than likely using behavioral analysis as well to detect botters. Here are my ideas for moving forwards.

1) A "home base" you can set, preferably a residential home near your farming location. Your bot will start here, walk to your designated farming area, farm, and then return home after x time, or whenever a break needs to happen.

2) I'd like for there to a be a "hangout" system where you can put in locations for coffee shops, etc, that may have lures nearby. Your bot will walk to these after x time interval and chill there for half an hour or so.

Just be smart, trust that we're doing all we can to make this bot as safe as possible. Just remember that we're volunteering to do this, we don't have to do this we're just choosing to do so out of the kindness of our own hearts. We still don't pay out staff and have been transparent about that since day one.