Tips on not getting soft-banned?

[brettstack]

I'm currently walking to, scanning, and attempting to catch at every 100m, but this results in me being insta-soft-banned - does anyone have tips on how to reduce the chance of being soft-banned? How slowly should I be performing these actions?

[cokeeffekt]

Hopping countries seems to trigger it for me, so avoid that.

[d-pollard]

Is the "soft ban" when they are fleeing instantly?

[cokeeffekt]

fleeing instantly is typically from multiple logins to the same account.

[d-pollard]

I think we should make some standards to kind of "detect" why things are happening

[cokeeffekt]

there is no event for why, we can guess, most of peoples problems stem from, multiple logins, hopping large distances too quickly, or not understanding async and triggering multiple events at once. Don't do these things and there shouldn't be an issue. Another thing to mention is the examples.js doesn't take async into account.

[d-pollard]

@cokeeffekt I don't even use this library any more. I forked it and made it way better lol.

[cokeeffekt]

@d-pollard if its way better why not submit a pull request

[d-pollard]

@cokeeffekt - our repos have deviated significantly. Others usually end up putting my code in here. My repo uses promises and I am moving to ES6, whereas this one wants to stay with ES5 only.

[cokeeffekt]

eh, i dunno i looked at your repo doesn't seem to be worth the swap. also most of the cb functions are promisify safe (a few need fixing) seems like time would be better spent working with the core project, rather than forking to start your own party. Esp since my latest pull requests you are falling behind on features. I only have more to come :P

[d-pollard]

@cokeeffekt - your features are childsplay whilst I'm busy working on fort take over and eventual - fort "DOP" (denial of play) for rival teams.

[jaredallard]

Commenting code wise, I can somewhat agree that the state of this repo is concerning. The amount of technical debt in this lib is insane, the convention is a bit odd, using callback constructors but then using the same instance as opposed to returning a new one.

IMO a fork would be nice of this, but not of the current state.

Tips soft ban wise -- noticed that keeping requests at a similar pattern of the app works nicely, deviation of reasonable walking time as well, basically think like the app prevents most of it.

[d-pollard]

Also, adding in lodash is overhead that this already - large library doesn't need.

[jimmywarting]

@d-pollard if you want to work with ES6 and promises - have a look at pokemongo-api

[brettstack]

What is fort DOP? I agree with Patrick, it makes more sense to keep it to one repo. While I prefer ES6 and promises, it's not worth forking the community over. It's also a little rude to call someone's PRs childs play...

On Mon, 25 Jul 2016, 03:29 Jimmy Karl Roland Wärting, < notifications@github.com> wrote:

@d-pollard https://github.com/d-pollard if you want to work with ES6 and promises - have a look at pokemongo-api https://github.com/stoffern/pokemongo-api

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Armax/Pokemon-GO-node-api/issues/127#issuecomment-234918009, or mute the thread https://github.com/notifications/unsubscribe-auth/ABy6l9YdpN7IvuabpEWNuGCD35oK4L6Oks5qZJAJgaJpZM4JTyQ- .

[Armax]

we are working on a more realistic walk function

[d-pollard]

@breandr ...I literally explained DOP right after I coined the acronym.

[brettstack]

And yet you didn't provide sufficient explanation of "Denial of Play". If you're going to try coin new terms, you should probably make it clear what they mean. :)

[d-pollard]

@breandr any developer knows what a "Denial of..." means...seems to me like you like to play the role...

[d-pollard]

Hell, anyone who knows English could figure out what it means lmfao @breandr