I've been playing a lot recently because I recursed and set myself a short deadline for getting back to 16. I can't even begin to tell you how many times I've capped a portal then tried to mod it and the cap hadn't registered yet. I've also had countless cases of bursters spinning on my screen for a long time despite having very solid cell service.
The APIs are the functions that get called when you perform an action in-game.
So hacking is one, deploying, etc...
What and how they improved the APIs (and which ones) is unknown, but there is hope it will decrease the time it takes to perform actions. (Reduce the "lag")
So let's just hope they improved the gameplay ones and not the scanning or Niantic social ones.
Ingress has a client-server architecture. The client is what lives on your phone. When you take any action in the game (and even when you don't) the Ingress client sends messages to the Ingress servers to get information and/or to send them information. For example, if you fired a burster the client would send that information to the Ingress servers, and the servers would respond with relevant updates. If you move around, the Ingress client will send messages to the server to get information about the map, XM on the ground, portals around you, etc. [insert a lot of handwaving because I'm speaking conceptually rather than with knowledge of the exact messaging structure]
The API is essentially the language that the Ingress client and servers speak to each other. It might go something like this:
CLIENT: Hey, I deployed a level 1 resonator on this portal
SERVER: Here is the new status of the portal (details about resos, mods, etc) and the amount of AP that was awarded for that deploy.
APIs can be complicated, and there are often ways that they can be optimized. They could be grouping requests that happen rapidly, sending/receiving less data on each request, or any number of other things.
TL;dr: Niantic made a change to the language that the scanner and servers speak to each other.
That's been a frequent issue for a few years now. ie Laggg It frequently annoys me enough that I don't want to recurse, I don't want to spend more time playing Ingress and being frustrated. Ingress is the thing I'd rather do and enjoy. If its just frustration, I don't do it.
InvestigateXM
✭✭✭✭✭
Comments
🤔
That's a huge win if it's effective.
I've been playing a lot recently because I recursed and set myself a short deadline for getting back to 16. I can't even begin to tell you how many times I've capped a portal then tried to mod it and the cap hadn't registered yet. I've also had countless cases of bursters spinning on my screen for a long time despite having very solid cell service.
Update which APIs?
Imagine (maybe you don’t have to) that I’m an idiot who has no idea what that all means and what changes to the API mean. Could you explain it simply?
The APIs are the functions that get called when you perform an action in-game.
So hacking is one, deploying, etc...
What and how they improved the APIs (and which ones) is unknown, but there is hope it will decrease the time it takes to perform actions. (Reduce the "lag")
So let's just hope they improved the gameplay ones and not the scanning or Niantic social ones.
An API is a library of algorithms which a programmer can call upon to use in their code base.
They can use one, some, most or all, of the algorithms in that API
And there can be several of these libraries that a project can use
Ingress has a client-server architecture. The client is what lives on your phone. When you take any action in the game (and even when you don't) the Ingress client sends messages to the Ingress servers to get information and/or to send them information. For example, if you fired a burster the client would send that information to the Ingress servers, and the servers would respond with relevant updates. If you move around, the Ingress client will send messages to the server to get information about the map, XM on the ground, portals around you, etc. [insert a lot of handwaving because I'm speaking conceptually rather than with knowledge of the exact messaging structure]
The API is essentially the language that the Ingress client and servers speak to each other. It might go something like this:
CLIENT: Hey, I deployed a level 1 resonator on this portal
SERVER: Here is the new status of the portal (details about resos, mods, etc) and the amount of AP that was awarded for that deploy.
APIs can be complicated, and there are often ways that they can be optimized. They could be grouping requests that happen rapidly, sending/receiving less data on each request, or any number of other things.
TL;dr: Niantic made a change to the language that the scanner and servers speak to each other.
That's been a frequent issue for a few years now. ie Laggg It frequently annoys me enough that I don't want to recurse, I don't want to spend more time playing Ingress and being frustrated. Ingress is the thing I'd rather do and enjoy. If its just frustration, I don't do it.
The meaning of "API" in that context is anybody's guess.
Look at all the open source licenses listed in the ingress settings. It could have been any of those, or something else entirely.
Niantic did not care to elaborate. Might as well be "minor text fixes"