In this tutorial series, we’ll be going through a few basic topics, we’ll be adding more topics as they are written.
This post will discuss where to look for codes.
Daily Codes are currently found on Niantic’s Investigation Blog. They are usually hidden within the source code of the page but some codes are found in an image associated with the post.
There are usually 3 codes per day and codes are released every day unless there is an Ingress Report.
There are various ways to access the source code of a page depending on your operating system and web browser. I’ll leave that up to you to figure out. On mobile, there isn’t an easy way to view the source code.
The codes will always be in-between the
<div id="entry-content"> and
</div><!-- .entry-content --> lines. Codes can be hidden at the end of URLs,
alt attributes, within
A good indication that a URL has a code is the presence of a
#. In a URL, anything after the
# is considered a fragment identifier. When you visit a URL with a fragment identifier, it visits the chosen URL (everything before the first
#), and would visit the section of a webpage that is identified by the fragment identifier, if it is there.
In the Where Ideas Come From post, the link for Operación Excalibur looks like this:
https://plus.google.com/events/cvsvpaa6lfpst7ovia1sqambgv8 is the page it is visiting
ohp5wpd6tp5s2etni is the code
Also from the same page, there is a link to the Synchronicity Wikipedia entry:
But there are 3 #, the first one in the URL separates the URL and code:
alt attributes are used in HTML
<img> tags to text when an image is not displayed.
id attributes are used in various HTML to name a block.
Looking at The Eruption of Vesuvius post, there is one image at the top of the page:
<img class="aligncenter size-large wp-image-1085" src="http://investigate.ingress.com/wp-content/uploads/2016/04/TheEruption-1024x951.png" alt="n13k23tn1137ufu3" width="1024" height="951" srcset="http://investigate.ingress.com/wp-content/uploads/2016/04/TheEruption-300x279.png 300w, http://investigate.ingress.com/wp-content/uploads/2016/04/TheEruption-768x714.png 768w, http://investigate.ingress.com/wp-content/uploads/2016/04/TheEruption-1024x951.png 1024w, http://investigate.ingress.com/wp-content/uploads/2016/04/TheEruption.png 1200w" sizes="(max-width: 1024px) 100vw, 1024px" />
alt="n13k23tn1137ufu3" and the code is
<span> tags are places in a blog post where codes can be found.
Looking at the Oliver Lynton-Wolfe Missing post:
<span style="display: none; font-size: 4px;">htmamip3hseh27r2</span>
Sometimes, there are clues within the
<span> tag attributes. In this example,
font-size: 4px; is a clue.
Certain symbols are sometimes encoded in HTML entities, most notably the
In PAC’s Weekly Wrap-Up: April 24, 2016, one of the codes is a URL:
& is the entity that converts into
&, and it must be converted before a code solve attempt.
There are other entities that are used and you can find a HTML entity decoder to convert these.
Sometimes code are embedded into images.
The original image is on the left, with the right one having highlights where the codes are found.
Ingress Reports usually have 3 codes in the episode and are available as annotations. Waiting for annotations to display on screen is tedious so there is a shortcut available.
The annotations are available as XML. For the Ingress Report on April 24 2016 (Aegis Nova Revealed), the link to the video:
and the link to the annotation:
Change the end of the annotation URL to match the video URL and you can get any video’s annotation XML.
Inside the XML, the codes are usually within the <TEXT> tags.
<TEXT>--... .. --. -. .---- .-.- --. .--- - .-.- --... -.. ..--- -...</TEXT>
However, sometimes, this is not enough for a complete solve (missing keyword, etc), and you must go back to the video at the annotation’s appearance for a hint. For example, for
ada3zc36qq3 (there is no keyword sub for this code), this is the relevant XML that tells you when the annotation appears:
<rectRegion d="0" h="7.8220000267" t="1:05.259" w="25.8719997406" x="6.33900022507" y="3.36599993706"/>
<rectRegion d="0" h="7.8220000267" t="1:10.300" w="25.8719997406" x="6.33900022507" y="3.36599993706"/>
The annotation first appears at 1 minute 5 seconds in the video and disappears at 1 minute 10 seconds.
Word of the Day
Word of the Day codes are also usually found in the source code and the majority of them are inside
<code> tags. Sometimes they are hidden elsewhere: inside the
<style> tag, in a
<meta> tag, inside comment tags (
-->), maybe even the background image itself.
Anomaly Codes are announced by Verum Inveniri and the location of such codes changes each time.