API has been *****ed.
- Thread starter Theory
- Start date
JoelGilmor
New Member
- Joined
- Aug 31, 2016
- Messages
- 176
- Reaction score
- 1
sounds like FPM couldn't resolve the hash function. But he found a way to emulate it without having to reverse it. I don't know if that was the solution hatching egg was looking for.
No it is not, and they are not going to use it after all.
From Dutchdefender's explanation, they just copied Niantic's hashing function and incorporated it to theirs instead of fully reverse engineering it which raised copyright issue concern.
Waiting continues, Reverse Engineering effort continues.
From Dutchdefender's explanation, they just copied Niantic's hashing function and incorporated it to theirs instead of fully reverse engineering it which raised copyright issue concern.
Waiting continues, Reverse Engineering effort continues.
Mew2
Member
- Joined
- Sep 10, 2016
- Messages
- 277
- Reaction score
- 2
FastPokeMap going live on Sunday, the new API is cracked | Pokemon GO Hub r a c k e d/
Breaking news everyone, Reverse Engineers behind FastPokeMap just announced on Twitter that the map is going live in two days max! FastPokeMap will live again
“good news, one of the #RE helper *****ed it fully, bad news; he went to sleep. What does it mean? FPM will come back within 2 days max.” – @FastPokeMapCom
Twitter is down at the moment, it’s under DDOS attack on their DNS servers, so it will take you a while to load the links and search through the broken page layout.
This is great news, as community salt levels are over the top, with hundreds and hundreds of reddit threads popping up daily and commenting on the tracking issues.
Also, this means all of the tracking apps are coming back online, as the FPM API will be made public by the author!
Update: The FastPokeMap developers have just successfully obtained a response from the Niantic servers. Pictured below, good job boys!
Breaking news everyone, Reverse Engineers behind FastPokeMap just announced on Twitter that the map is going live in two days max! FastPokeMap will live again
“good news, one of the #RE helper *****ed it fully, bad news; he went to sleep. What does it mean? FPM will come back within 2 days max.” – @FastPokeMapCom
Twitter is down at the moment, it’s under DDOS attack on their DNS servers, so it will take you a while to load the links and search through the broken page layout.
This is great news, as community salt levels are over the top, with hundreds and hundreds of reddit threads popping up daily and commenting on the tracking issues.
Also, this means all of the tracking apps are coming back online, as the FPM API will be made public by the author!
Update: The FastPokeMap developers have just successfully obtained a response from the Niantic servers. Pictured below, good job boys!
21 October, GMT +0, 15:45 - A succesful ping has been made! The devs did it.
This means they succesfully reverse engineered the neccesary parts of Niantics code. Now there is not an API yet, but FPM will 100% come back. Probably within 48 hours. For everyones scanners to come back they would have to build a public API and release it. Their first ping was probably made with a lot of manual guidance, automating the process (building the API) won't take terribly long. Last time it took them 9 hours or so, it might be longer this time (less devs should hurt this part especially).
The API uses Niantics isolated hashing function. It has not been reverse engineered, but they isolated the part that does the code. This is legally "stealing" code from Niantic and distribution (if they want to share their API fix) will be harder. Hosting this code is C&D worthy if I am correct. This is in the end a losing war for Niantic though, last time they C&Ded someones map it had a couple of thousand downloads..
For now.. They did the hard part, what is left is easy stuff, Hooray!
21 October, GMT +0, 16:00 - Heard that the devs do intend on releasing a public API, still not 100% confirmed, but I'd put my money on it.
22 October, GMT +0, 00:00 - Today was a great day, the API is coming.
With the API done, I am not done writing.. yet.
Legal issues
The solution of the devs isn't the cleanest one, Niantic will have a strong copyright position against anyone directly using the API. IE: host your map. FPM users will be safe. I am not sure how FPM intends to go about this.
Why was the previous API solution "legal" and this one "illegal"?
Niantic has made pokemon go and within that there is the part that contructs "unknown6". In the end constructing unknown6 is just a series of computations of 1's and 0's, math. You can not patent 2+2, neither can Niantic patent the way in which unknown6 is made. With the first API-***** the devs made their own Unknown6. The reverse engineered the math behind 2+2 (unknown6) and made an application which did 2+2.
Now what you can patent is the way in which you write 2+2, to further my example: the font. In terms of code these are comments/white space/variable names/ etc. During the first API break they wrote their own 2+2, but now it is slightly different.
The devs had trouble reverse engineering the hashing function. Therefore they just "stole" the hashing function from Niantic. They isolated the part that does the hashing function and copy-pasted it into their solution. This means they also are using the "font" that Niantic uses, which makes the solution prone to copyright claims.
22 October 2016, GMT +0, 02:30 - The devs think the legal issue is too big to pass on, If I understand correctly they will attempt to reverse the hashingfunction after all. They will only release the API after that, (another 99% confirmation that the API will indeed be public).
The long wait continues. reengineering effort continues.
This means they succesfully reverse engineered the neccesary parts of Niantics code. Now there is not an API yet, but FPM will 100% come back. Probably within 48 hours. For everyones scanners to come back they would have to build a public API and release it. Their first ping was probably made with a lot of manual guidance, automating the process (building the API) won't take terribly long. Last time it took them 9 hours or so, it might be longer this time (less devs should hurt this part especially).
The API uses Niantics isolated hashing function. It has not been reverse engineered, but they isolated the part that does the code. This is legally "stealing" code from Niantic and distribution (if they want to share their API fix) will be harder. Hosting this code is C&D worthy if I am correct. This is in the end a losing war for Niantic though, last time they C&Ded someones map it had a couple of thousand downloads..
For now.. They did the hard part, what is left is easy stuff, Hooray!
21 October, GMT +0, 16:00 - Heard that the devs do intend on releasing a public API, still not 100% confirmed, but I'd put my money on it.
22 October, GMT +0, 00:00 - Today was a great day, the API is coming.
With the API done, I am not done writing.. yet.
Legal issues
The solution of the devs isn't the cleanest one, Niantic will have a strong copyright position against anyone directly using the API. IE: host your map. FPM users will be safe. I am not sure how FPM intends to go about this.
Why was the previous API solution "legal" and this one "illegal"?
Niantic has made pokemon go and within that there is the part that contructs "unknown6". In the end constructing unknown6 is just a series of computations of 1's and 0's, math. You can not patent 2+2, neither can Niantic patent the way in which unknown6 is made. With the first API-***** the devs made their own Unknown6. The reverse engineered the math behind 2+2 (unknown6) and made an application which did 2+2.
Now what you can patent is the way in which you write 2+2, to further my example: the font. In terms of code these are comments/white space/variable names/ etc. During the first API break they wrote their own 2+2, but now it is slightly different.
The devs had trouble reverse engineering the hashing function. Therefore they just "stole" the hashing function from Niantic. They isolated the part that does the hashing function and copy-pasted it into their solution. This means they also are using the "font" that Niantic uses, which makes the solution prone to copyright claims.
22 October 2016, GMT +0, 02:30 - The devs think the legal issue is too big to pass on, If I understand correctly they will attempt to reverse the hashingfunction after all. They will only release the API after that, (another 99% confirmation that the API will indeed be public).
The long wait continues. reengineering effort continues.
Last edited:
JoelGilmor
New Member
- Joined
- Aug 31, 2016
- Messages
- 176
- Reaction score
- 1
I had never tried catching Pokémon using a bike. I tried this morning. I have to say, it's really fun having the ability to quickly move from one block of the street to the other trying to find one using the sightings.