-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
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. |
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. |
The new login/session handling should deal with those issues, but I need more testing. |
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. 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 😉) |
@WallyCZ found out some differences between the original client and our app, he's working on it. |
I was just thinking of possible problem with our aproach in storing authtoken:
The text was updated successfully, but these errors were encountered: