Taking a page from Yik Sheng Lee's playbook, and reposting a recent comment of mine to a Niantic Project thread, so...
Taking a page from Yik Sheng Lee's playbook, and reposting a recent comment of mine to a Niantic Project thread, so that those here can comment directly:
====================
Lets talk about the portal discovery process and the implications of being a seer for a bit. You come across a piece of artwork and say to yourself "That has to be a portal" but when you check your scanner, nothing is shown.
So you submit it, and after some time, you get an email back from NIA SuperOps or Ingress Operations or whatever they're calling themselves this month, and it says "Success" and now sure enough that piece of artwork now shows a portal the next time you go by that spot with your scanner.
This is the part that I think some agents get confused on. Even though the label on the long-press gesture menu on the scanner says "New Portal" NIA SuperOps/Ingress Operations doesn't send out a portal construction team to come out and weaken the fabric between dimensions to make a portal at that spot. We don't have that technology.
The portal was already there and has always been there. (Or may have recently moved there, if Lightman's observations on moving portals are accurate.)
The reason it didn't show on your scanner is that each portal (and the XM spilliage it emits) has its own unique signature frequency, and the scanner didn't know to look for that signature until it got added to the Intel Package that gets downloaded to your scanner each time you start it up.
So if portals are there whether or not they're listed in the Intel Package, and all that's needed for the Shapers to pattern an XM Entity copy of someone is for that person to "bask in the presence of XM" and "spend time at the portals", why would Jarvis say here that "The Scanner is the key"? What difference does the Scanner make?
The difference is Control Fields, which project the influence and XM of a portal over a much wider area, extending it to places that aren't near any portal.
So what of the "false portals" that are mentioned, what does Roland refer to there? I believe that this stems from the fact that our methods for detecting unique XM signature frequencies aren't entirely accurate yet, especially with the remote sensing techniques that Ingress Operations must employ.
These satellite surveys have already picked up a trace background noise of XM that does not seem to be associated with any particular portal; these may be residuals from Lightman's moving portals, sensor echos of portal-associated XM that is located in another location, or they may be leaks in the dimensional fabric too small to be classified as full portals. And again, we only see XM that matches a frequency in the Intel Package, there is likely a lot more Background XM that is undetected.
Some Agents try to game the system, using these traces of Background XM to try to trick Ingress Operations into marking a location as a portal when there's no proper portal there. Links and fields created off of these false portals still spread the touch of XM, but without any intelligent force behind it to guide and moderate the effect. The effects of this are unknown and unpredictable.
No matter what your feelings are of Roland Jarvis and his Shaper friends, this warning against false portals should be heeded by both factions. If you think a city has too many cars on the road, causing smog, noise pollution, and putting pedestrians at risk of being run over, sticking more cars on the road, driverless, with bricks on the accelerator pedals is not a solution. Sure, it makes it harder on the other drivers, but you're going to aggravate all of the problems you're trying to curb before you frustrate those drivers into staying home.
====================
Lets talk about the portal discovery process and the implications of being a seer for a bit. You come across a piece of artwork and say to yourself "That has to be a portal" but when you check your scanner, nothing is shown.
So you submit it, and after some time, you get an email back from NIA SuperOps or Ingress Operations or whatever they're calling themselves this month, and it says "Success" and now sure enough that piece of artwork now shows a portal the next time you go by that spot with your scanner.
This is the part that I think some agents get confused on. Even though the label on the long-press gesture menu on the scanner says "New Portal" NIA SuperOps/Ingress Operations doesn't send out a portal construction team to come out and weaken the fabric between dimensions to make a portal at that spot. We don't have that technology.
The portal was already there and has always been there. (Or may have recently moved there, if Lightman's observations on moving portals are accurate.)
The reason it didn't show on your scanner is that each portal (and the XM spilliage it emits) has its own unique signature frequency, and the scanner didn't know to look for that signature until it got added to the Intel Package that gets downloaded to your scanner each time you start it up.
So if portals are there whether or not they're listed in the Intel Package, and all that's needed for the Shapers to pattern an XM Entity copy of someone is for that person to "bask in the presence of XM" and "spend time at the portals", why would Jarvis say here that "The Scanner is the key"? What difference does the Scanner make?
The difference is Control Fields, which project the influence and XM of a portal over a much wider area, extending it to places that aren't near any portal.
So what of the "false portals" that are mentioned, what does Roland refer to there? I believe that this stems from the fact that our methods for detecting unique XM signature frequencies aren't entirely accurate yet, especially with the remote sensing techniques that Ingress Operations must employ.
These satellite surveys have already picked up a trace background noise of XM that does not seem to be associated with any particular portal; these may be residuals from Lightman's moving portals, sensor echos of portal-associated XM that is located in another location, or they may be leaks in the dimensional fabric too small to be classified as full portals. And again, we only see XM that matches a frequency in the Intel Package, there is likely a lot more Background XM that is undetected.
Some Agents try to game the system, using these traces of Background XM to try to trick Ingress Operations into marking a location as a portal when there's no proper portal there. Links and fields created off of these false portals still spread the touch of XM, but without any intelligent force behind it to guide and moderate the effect. The effects of this are unknown and unpredictable.
No matter what your feelings are of Roland Jarvis and his Shaper friends, this warning against false portals should be heeded by both factions. If you think a city has too many cars on the road, causing smog, noise pollution, and putting pedestrians at risk of being run over, sticking more cars on the road, driverless, with bricks on the accelerator pedals is not a solution. Sure, it makes it harder on the other drivers, but you're going to aggravate all of the problems you're trying to curb before you frustrate those drivers into staying home.
Comments
Post a Comment