API change details with actual source article....

[iitreatedii]

Pokemon Go: API Scanning Time Doubled! See how this effects you - Anime Blog

There you go...so now, 10 seconds -_____-

[mugendc4]

The whole API changed and 10 sec scanning was just part of the change...

[Pepejson]

10 second delay was like 24h ago and you didn't scen noticed.
I'll told you that less pokemons was because of that but API change that happened 2-3hours ago actually changed everything


Wysłane z iPhone za pomocą Tapatalk

[Stupendous]

This is not the API change that happened today, the API change today blocks API calls. They most likely found a way to detect non-clients and instead of blocking their requests, they are sending empty responses. Which means bots and scanners don't work, unless some bypass is found.

[ZeroDayGhost]

This is not the API change that happened today, the API change today blocks API calls. They most likely found a way to detect non-clients and instead of blocking their requests, they are sending empty responses. Which means bots and scanners don't work, unless some bypass is found.

Man... I'm getting more intrigued about this by the second.

If what you're saying is true... Then, one would need to connect their phone that has Pokemon GO on it to their own WiFi. Get wireshark on android. Fire up wireshark, start sniffing, then fire up Pokemon GO, to see what's being sent between the app and the server. From there see if there are things that identify that it's phone (maybe MAC address (they can identify manufactures, not sure how specific they can ID a device - I know XBox 360s can be ID'ed by their MACs), maybe just a plain "HTC Desire X" in the packet), then implement the same identifiers in the bot's responses.

[JazzaaR]

I can tell you now, otakuart know nothing. This has been a thing since 0.31.

[NexLegend]

The article posted is directed to a "non-cheating" audience. Why do you think they would even talk about the API being completely changed. The 10 second thing is relevant to everyone, even if it wasn't updated today exactly lol.

[Fadelol]

Man... I'm getting more intrigued about this by the second.

If what you're saying is true... Then, one would need to connect their phone that has Pokemon GO on it to their own WiFi. Get wireshark on android. Fire up wireshark, start sniffing, then fire up Pokemon GO, to see what's being sent between the app and the server. From there see if there are things that identify that it's phone (maybe MAC address (they can identify manufactures, not sure how specific they can ID a device - I know XBox 360s can be ID'ed by their MACs), maybe just a plain "HTC Desire X" in the packet), then implement the same identifiers in the bot's responses.

Last thing i read on reddit was that they seem to have updated the API a couple of days ago but kept legacy support for older clients. With the latest update they forced client updates (if you were on a too old client without support for the new API) and disabled the legacy support. That said, there could still be some type of authentication used between server / client. I doubt it would be based on MAC-address/manufacturer/device though. It seems like that would be too easy to spoof to be worth implementing.