Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Discussion) Possible bans with our authtoken aproach #3

Open
jakubsuchybio opened this issue Aug 16, 2016 · 5 comments
Open

(Discussion) Possible bans with our authtoken aproach #3

jakubsuchybio opened this issue Aug 16, 2016 · 5 comments

Comments

@jakubsuchybio
Copy link
Contributor

I was just thinking of possible problem with our aproach in storing authtoken:

  • When you store authtoken, it acts as if you logged in once until the token expires. Now when we close the app, and enter in before 30minutes at some distant location(like traveling in car could make 50km diff), when token expires, then to the niantic this looks like teleport maybe?
  • Shouldn't we always at suspension and closing be logging out to prevent this?
  • Or in future support background worker to allow suspended app still run in background thread, so position and other things will be still updating?
@robertmclaws
Copy link

I don't think Niantic has a background worker on iOS, so I don't think we should have one either. I'm not sure whether their code logs out on suspension or disconnect, either. What I DO think is that we need to have protections to make sure we're not accidentally spamming their API. Situations like here ST-Apps/PoGo-UWP#884 are a good example... making sure we only try to re-login a certain number of times before we tell you to try again in a few minutes.

@jakubsuchybio
Copy link
Contributor Author

Well I read about some wrist thing. It has just one button and some color LED and you can actualy log into Pokemon Go and gather pokestops with one button and also catching pokemons with it... That's crazy cheating to me for some $$$...

However I too think that android doesn't have this functionality, so we should probably just stick with logging out and saving credentials for next openning and logging in again.

And I agree, that we should make these logins with timers to protect our users.

@ST-Apps
Copy link
Contributor

ST-Apps commented Aug 16, 2016

The new login/session handling should deal with those issues, but I need more testing.

@DarkAngelFR-zz
Copy link

Only ban I'm aware of by some people I fully know and trust : they used some bots and/or IV calculator websites with their account.
One guy told me he got ban with no cheat and playing only on his iPhone, then after talking turns out he logged once on a website with his account to have those hidden info on pokemon.....
From start of PoGoUWP I'm using two accounts (one for play, one for dev) none got banned. The dev account is teleporting a lot and almost never connect to official app, the play one is sometimes being used on android (to clean inventory).

I'm not sure ban comes from our app, anyway good to protect as much as possible (@ST-Apps if you need specific testing do not hesitate 😉)

@ST-Apps
Copy link
Contributor

ST-Apps commented Aug 17, 2016

@WallyCZ found out some differences between the original client and our app, he's working on it.

This was referenced Aug 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants