Na dann kann ich ja nach dem Aufstehen wahrscheinlich direkt wieder die Bots anwerfen. Ich bin mal gespannt. Schön das es Leute gibt, die immer fleissig daran arbeiten. ;)
Pokemon GO API changes - Bots aren't working for now
08/05/2016 02:26
calrogk#106
08/05/2016 02:28
RoFu#107
Niantic ist wohl schon informiert, und wissen Bescheid
Ich denke das wird wieder nicht lange dauern. Niantic will die Bots mit aller Macht aussperren, und wenn die Ingresslösung nicht funktioniert werden sie was neues entwickeln.
Die wollen Geld mit Pokemon Go verdienen, ich denke die werden noch sowas wie: Bezahlte Pokemon im ingameshop bringen -.-
Das einzige was sie nicht verhindern können ist das Spielen über Nox und ähnliches :-)
Ich denke das wird wieder nicht lange dauern. Niantic will die Bots mit aller Macht aussperren, und wenn die Ingresslösung nicht funktioniert werden sie was neues entwickeln.
Die wollen Geld mit Pokemon Go verdienen, ich denke die werden noch sowas wie: Bezahlte Pokemon im ingameshop bringen -.-
Das einzige was sie nicht verhindern können ist das Spielen über Nox und ähnliches :-)
08/05/2016 02:29
Akiyama Mio#108
Da wäre ich mir nicht sooo sicher ^^ In dem DiscordQuote:
Na dann kann ich ja nach dem Aufstehen wahrscheinlich direkt wieder die Bots anwerfen. Ich bin mal gespannt. Schön das es Leute gibt, die immer fleissig daran arbeiten. ;)
wo ich die ganze Zeit bin von dem Reddit Thread ->
[Only registered and activated users can see links. Click Here To Register...]
Die Prügeln sich die ganze Zeit mehr als dass sie versuchen
das Problem zu beheben ^^ Also mit Morgenfrüh rechne ich
keinesfalls.. Wenn überhaupt Morgen Abend...
Also Freitag Abend
WooooW... Hat ja keiner mit gerechnet dass die EntwicklerQuote:
Niantic ist wohl schon informiert, und wissen Bescheid
wissen dass die Coder der Bots nicht soo einfach aufgeben ^^
08/05/2016 02:35
RoFu#109
Niantic wird vorallen wieder wie viele andere Entwickler erst mal die User bestrafen und sich vermutlich dann langsam an die Botentwickler ranmachen.Quote:
wissen dass die Coder der Bots nicht soo einfach aufgeben ^^
Für die spieler bringt das alles nichts....
08/05/2016 03:05
LdsLopt#110
ist ja das was ich meinte in den nachrichten wird das ja alles Public deswegen wissen es die Entwickler in sehr sehr kurzer zeit auch alles
08/05/2016 03:32
TheCrytec#111
wie isn der aktuelle stand wenns möglich ist in deutsch ^^
08/05/2016 03:50
PewPewLaZerGun5#112
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.
PERSONAL STATUS: I am going to catch a couple of pokemon I will update once more before going to sleep.
------------------
Bedeutet soviel wie es kann noch etwas dauern
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.
PERSONAL STATUS: I am going to catch a couple of pokemon I will update once more before going to sleep.
------------------
Bedeutet soviel wie es kann noch etwas dauern
08/05/2016 07:16
INakedSnakeI#113
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: [Only registered and activated users can see links. Click Here To Register...] && [Only registered and activated users can see links. Click Here To Register...]
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.
For now I am going to sleep. We have opened a channel for API-updates [Only registered and activated users can see links. Click Here To Register...], the updates in the chat will probably be a bit more tech-heavy. I will be back for translations to English tomorrow.
:pimp::pimp::pimp:
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: [Only registered and activated users can see links. Click Here To Register...] && [Only registered and activated users can see links. Click Here To Register...]
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.
For now I am going to sleep. We have opened a channel for API-updates [Only registered and activated users can see links. Click Here To Register...], the updates in the chat will probably be a bit more tech-heavy. I will be back for translations to English tomorrow.
:pimp::pimp::pimp:
08/05/2016 07:25
CC3#114
ich glaube soweit ich es gelesen habe, noch nichts neues leider -.-Quote:
08/05/2016 07:45
sysadminroot#115
Das sind die aktuellen NEWS !!!!
08/05/2016 08:10
DemoPresent#116
Kann man eigentlich nachvollziehen, ob jemand über NOX ins PoGo loggt?
Oder ist das wirklich unersichtlich für Niantic ob das NOX oder ein normales Smartphone ist?
Oder ist das wirklich unersichtlich für Niantic ob das NOX oder ein normales Smartphone ist?
08/05/2016 08:28
Scrypton#117
Na dann solltest du dem Dev-Team mal zeigen wo es lang geht... :rolleyes:Quote:
Du ladest dir die APK, entpackst diese, decompilierst die smali files bzw. deobfuscatest dann noch.
08/05/2016 08:30
aKaToti#118
Jo deswegen ist der Code auch so beschissen und die Performance auch so schlecht :DQuote:
Da sehe ich mit meiner Ausbildung zum Fachinformatiker (die schon 10J her ist und vor dem Studium war) ziemlich alt aus
Ernsthaft die haben an einigen Stellen geschlampt da wird einen uebel
08/05/2016 08:44
luppa88#119
Current Status:
Contents of Unknown6 has been intecepted at known subroutine.
New Proto Found inside Unknown6.Unknown2.Unknown1! Not all fields (at least 11 fields) have been resolved at the moments. Devs are working hard on it.
Contents of Unknown6 has been intecepted at known subroutine.
New Proto Found inside Unknown6.Unknown2.Unknown1! Not all fields (at least 11 fields) have been resolved at the moments. Devs are working hard on it.
08/05/2016 09:05
PeterPan2454#120
ich meinte die devs von githubQuote:
Ernsthaft die haben an einigen Stellen geschlampt da wird einen uebel