maierfelix / maierfelix/POGOserver
Creating a technical insight article
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 476
- Forks
- 198
- PR merge metrics
- No merged PRs in 30d
Description
Hello POGO fans,
Last year I worked on this emulator for a few months. I started the project immediately after all the bots stopped working (u remember?:p). It was one of the most fun projects I've ever worked on, especially the emulator's API which allows to place pokestops, gyms and spawns in realtime on google maps.
The project is abandoned because of Niantic's drastic client changes for version > 0.35. The client source and networking is hard to decrypt as well as it's very tricky to bypass SafetyNet. Also there were crowds of people intentionally claiming authorship, selling the source and so on. You can thank these people too :-)
**TDLR;** I'd like to ask here if there is a interest in reading an article about the creation of this project - about the hard parts and the fun parts with a technical view on it. Submit a vote by giving a 👍
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry point. Start by clarifying the article's technical scope and publication location; done would be an agreed, completed technical insight article about the project's creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100