8787 build

[Mad4poko]

SUMMARY/UPDATE

GMT +1, 23:30 (sorry wrong timestamp previously) - We have much of the encryption understood. We however still dont know, how exactly the input is stored (protobuffer), this issue is very complicated. This is needed to track down the remaining inputfields.
GMT +1, 01:30 - We've got the encryption fully working (although we dont fully understand it)! You could call this breakthrough #3. The primary thing we are working on is getting the protobuffer.
This is a journey for me also. It is hard to keep up with what the devs are doing. What is a "protobuf format" for example? I am told it sits between the input and the encryption. It takes the inputvalues, rearranges them and sends them off for encryption. Like a blueprint for the inputdata.
Now we have the encryptionpart fully working, but we cannot backtrack to the input because we dont know how the blueprint arranged the inputvalues. Therefore we are making our own blueprint (protobuf-format)! Backtracking one step at a time. As we work on our protobuff format the input will become clear hopefully.
GMT +1, 03:30 - No major news. We're working on it and making progress.
I do want to make this another moment of reflection, the logistical nightmare of getting a community to work together like it has. It was a nightmare, without a clear solution, where the mods had no "good" choice.
It started off small: an open discord channel in which everyone could talk, working together to fix the API. It became clear this wasn't as easy as we thought.
Meanwhile the amount of people in the channel talking grew and grew. This however led to huge amounts of spam, most commonly "When is the API ready/What happened with the API". The situation became unworkable and we had to restrict talking rights on the discord.
This situation also became unworkable, people were claiming our progress as their own and they were also giving the community false hope as in how fast a new API would be made. On top of that the mods were still being spammed to death with requests for talking rights in the channel. We decided to hide the channel completely.
We tried a secondary channel, in which people could prove themselves worthy. But this channel started to get the same problems as the primary channel had initially. As well as people in the channel being understandibly angry at the mods, because they had no access to our primary channel they were doing the work we did hours ago.
Right now we are moving to transparancy again. We made the primary channel readable for everyone again. And hopefully noone will abuse this. We have also made an open-to-everyone github: https://github.com/pkmngodev/Unknown6 && https://github.com/pkmngodev/Unknown6/wiki
What can we learn from this though? I think there is no "solution" to this problem. Instead I want to thank the mods for putting in ridiculous amounts of work, merely to ease the pain of an unsolvable situation.

From Reddit pokemongo/dev

[Mad4poko]

https://map.goradar.io

Working on and off some times, yesterday was giving 100% pokemon check, I'm android and having some problems to location set, IOS working better

[hjyg]

SUMMARY/UPDATE
As well as people in the channel being understandibly angry at the mods, because they had no access to our primary channel they were doing the work we did hours ago.
Right now we are moving to transparancy again. We made the primary channel readable for everyone again.We have also made an open-to-everyone github

When the bot developers are more legit than the game developers themselves, you know something's not quite right.

Good on ya boys.

[Mad4poko]

SUMMARY/UPDATE 05 August

5 August 2016, GMT +1, 13:00 - This is a cool tech-read on what we're doing right now: https://github.com/pkmngodev/Unknown...ment-237754201
GMT +1, 13:30 - No major news: right now it's a grind. We're working on the protobuf, we've renamed some more fields succesfully but there is still a big chunk of unknown left. We've also made progress on mapping all the functions that are called in the encryption, we are working to fully understand the encryption. Tracking the output back towards input is proving to be a tricky and tedious job.
I will also be answering some comments. Quick FAQ:
Q: I think I am qualified, how can I join to help?
A: I am sorry, but at the moment the primary channel is not open for applications. You can help however, we have a public repo where you can contribute and make a pull request: https://github.com/pkmngodev/Unknown6/wiki && https://github.com/pkmngodev/Unknown6.
Q: The devs should try x.
A: I have no idea what you're talking about, but I am sure the devs have thought of it. If you really think you have a brilliant discovery be sure to pass it on somewhere in the discord.
GMT +1, 15:30 - No major news again on the coding front, which was expected, its a grind.
I am updating to tell you that we've set up a reddit live thread: https://www.reddit.com/live/xdkgkncepvcq. The reddit livethread will contain more technical updates, expect to see terms you dont understand if you are not an experienced coder. If the devs don't update it they are busy coding. We've also set up a twitter, which will more accessible in terms of language. The twitter can be found at: https://twitter.com/pkmngodev, I will tweet whenever I update this comment (and they've given me access) They put me in charge of the Twitter.
We've also made the discord invite permanent, should not expire anymore, *fingers crossed*.
We want to keep you guys updated as well as not giving any room for fake twitter accounts.
5 August 2016, GMT +1, 16:00 - We have uncovered another field of the input! It feels good to have some progress finally. Don't get your hopes up YET, we still have another field to go, we are working to crack that too.
GMT +1, 17:00 - We have fully confirmed the earlier mentioned field of the input. Everyone is in a good mood, we're making progress.
GMT +1, 18:00 - We think the field we are trying to crack if connected to the field we just cracked. Hopefully that helps us.
GMT +1, 19:00 - We would like to repeat that the API-cracking community does not support bots. We are here to crack the API, thats it. That said we would like to confirm that Niantic can detect any MITM apps, these are apps that somehow modify data sent to the server. For example an app that ensures a perfect pokeballthrow. If you used an app like that Niantic could know.
We do not know whether you'll get banned for using such an app, we merely confirmed that Niantic could (theoretically) detect it. And it is not our concern, our concern is cracking the API.

UPDATE from Reddit pokemongodev

[Mad4poko]

https://www.reddit.com/live/xdkgkncepvcq/

For update from LIVE Reddit thread for pokemongodev

[valebiets]

https://www.reddit.com/live/xdkgkncepvcq/

For update from LIVE Reddit thread for pokemongodev

thank you for the info, sorry can't help and good luck for them...

[Mad4poko]

Just in

Hey /r/pokemongodev community,
After a productive day and impromptu teamwork by the community developers; out of 4 remaining unknown new portions of the requests, we have discovered how to generate 3. One more to go.
The only remaining request is well understood, so we should have a request generator working soon.
This means, we're very close to finishing and we'll have the API complete and functioning shortly.


Almost there guys

[everlasting01a]

Just in

Hey /r/pokemongodev community,
After a productive day and impromptu teamwork by the community developers; out of 4 remaining unknown new portions of the requests, we have discovered how to generate 3. One more to go.
The only remaining request is well understood, so we should have a request generator working soon.
This means, we're very close to finishing and we'll have the API complete and functioning shortly.


Almost there guys

Thank you for the up to date info. If you don't mind how about you make a standalone thread that informing about this case. It would be great help to many people who wants to know recently update

[valebiets]

Just in

Hey /r/pokemongodev community,
After a productive day and impromptu teamwork by the community developers; out of 4 remaining unknown new portions of the requests, we have discovered how to generate 3. One more to go.
The only remaining request is well understood, so we should have a request generator working soon.
This means, we're very close to finishing and we'll have the API complete and functioning shortly.


Almost there guys

already in the discord chat for 5 hours+ and trying to help them with logic cause I don't understand programming at all...

[RedLFC1892]

Thank you for the up to date info. If you don't mind how about you make a standalone thread that informing about this case. It would be great help to many people who wants to know recently update

If you want to keep up to date, all you have to do is look here:
https://www.reddit.com/live/xdkgkncepvcq/

[Mad4poko]

http://www.ownedcore.com/forums/poke...own6-team.html

OK Guys new Thread everyone welcome to share

[dalgyte]

Why is this happening? Never used a bot before, and I think I'm softbanned :/

[xiulun]

would you read the 1st page pleaassseeee

[BIOABOMAI]

Anxious!

[Mad4poko]

http://www.ownedcore.com/forums/poke...n6-team-2.html (SUMMARY/UPDATE at API fix from Reddit Unknown6 Team)

Thread as been moved