Delivered-To: yuen.ni@nia.ts.gec Received from: 164.73.11.27 with SMTP id hbbafabcbffa; Received from: 73.239.11.27 with SMTP id acbabbbbbfab; Received from: x2.nia.ts.gec (x2.nia.ts.gec [66.239.11.27]) by x2.nia.ts.gec with ESMTPS id njkf.p66191n.4.19.12.48.46 (version=TLSv1/SSLv3 cipher=OTHER); by x2.nia.ts.gec with ESMTPS id njkf.p66191n.4.19.12.48.46 Received-SPF: neutral (nia.ts.gec: 18.239.11.27 client-ip=18.239.11.27;) Authentication-Results: x2.nia.ts.gec; spf=neutral ; dkim=pass (test mode) header.i=@nia.ts.gec Message-ID:<gbbhjaebbfabcbbfb@nia.ts.gec> Received from: 54.66.11.27 with SMTP id babbfabgfababacbffa; From: 'Dr. Ezekiel Calvin' <zeke.calvin@nia.ts.gec> Reply-to: <zeke.calvin@nia.ts.gec> Subject: Re: New Scanner updates? To: Yuen Ni <yuen.ni@nia.ts.gec> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary='944887877-8989469-00894=:887895'--898885-8879429-4494=:7881 Content-Type: text/plain; charset=us-ascii Director, All researchers are working on shutdown related tasks, however, I can confirm that the modifications to the Scanner are real. Links now seem to strengthen the defensive capability of Portals, and we are seeing the potential for XMPs to consume XM during the deployment phase, perhaps to stabilize the targeting mechanism. I have been unable to track how these upgrades were injected into the code. At this point, reverting the changes would take away from shutdown related tasks, I recommend we ignore the modifications for now. Regard the Data transmission on April 21. We are unclear if this is a hoax or real. The evidence points to Victor Kureze, but both Phillips and I have interviewed him, thoroughly, including a polygraph. The test does not indicate deception, making him either a very good liar, or the wrong guy. As far as I know, the whole concept is impossible. We can read the ordered data stream from the XM, but the write operation has never been achieved. Calvin "Yuen Ni" <yuen.ni@nia.ts.gec> wrote: Calvin, See the post below, came to me via Omnivore. What the hell is going on? Are we shutting down Niantic or are you playing games? Your primary role is to contain the researchers, lock down the data and wind down the project. ALL development tasks were to be put on hold pending our transition. NO NEW DEVELOPMENT. Are we completely 100% clear on this? Also what is this about Portal Data transmission? If itís true it blows a hole a mile wide in our site security plan. I donít need to remind you what that would mean for your career. Get control of the situation. Ni Attachments: Zokiev