pokemongo-api
pokemongo-api copied to clipboard
Help Wanted: Looking for some Moderators
Hi Im looking for some People to help moderating this Repo
Jobs todo:
- Reviewing Pull Requests
- Moderating Issues
Optional:
- Contributing
- Writing wiki Articles
I don't have really much time for moderating or writing wiki articles, but I'm up for contribute. It's by far the most up-to-date and awesome node api for PoGo and I simply love the async pattern. I've made some fixes before you came back on Github (like the file login cache read that I've seen you have already fixed) that I could make a PR from. For example, I included full support for SOCKS proxy (like tor) that helps to mitigate the Niantic soft-banning wave. Are there any issue/feature that needs to be fixed/implemented?
@Jamby93 there was a issue in the old repo about using potions on pokemon and proxy sounds nice if doesnt break stuff and is optional
just hit me up with a pull request if u like
Hey, i've archived saving last position and login token in separate files per account. It's not well tested yet. Maybe I find time some time next week to publish my work if someone is interested.
@DaVarga great thanks, sure just do a pull request when you want to
I can help out.. You all need to create PRs and keep this up to date if you want the best of the best..
Going private from repo is not the way to do it, then there would be no repo :angry:
@gallexme i can help out :wink:
Hey guys is this still going?
@gallexme
I've been busy for a few other projects, I should be able to come back developing on pogo soon though.
im busy with other stuff aswell
I found that source files are indented with 2 spaces, since I'm more familiar developing with 4 spaces indent is a problem changing to tabs indentation in order to let everyone choose their preferred tab space ?
@Jamby93 im also more the 4 space fan
I started with PR #16 that format with 4 space indentation, adds support to SOCKS proxy and locks node-pogo-protos to 1.2.0 due to an update in version 1.5.0 that breaks RequestEnvelope. I'm going to work to fix it properly with the updated protos. Who is going to review PRs, btw?
I see @stoffern is doing it, perfect. Going to push update of POGOProtos soon. It seems easier than I thought.
@Jamby93 i just did