Dismiss Notice
How Does This Work?

You create a free account and set a Gmail filter to forward your Ingress email damage reports.

The damage reports are processed in realtime into the Outgress analytics and alerting engine.

That's the short version.

Is This Allowed?

We believe so, but you decide.

But My Secret Data!

No one on the opposing faction cares who on their team is attacking you. Do you care who on your team is attacking opposing portals?

List Of Issues

Discussion in 'Bugs' started by digitalpoint, Oct 2, 2015.

  1. digitalpoint

    digitalpoint Administrator Staff Member Illuminator Enlightened L15

    Using this as a running list of issues.

    Cosmetic
    • Editor toolbar colors
    • Default font is terrible
    • Nothing on the root of the domain
    • Notification numbers get cut off on top of the page
    • Need to alter avatar model to take into account high resolution avatars (for retina/phone displays)
    • Global search function when on a page using the single line navigation bar
    Technical
    • Portal Group alerts
    • Individual agent perimeter alerts
    • Self-flipped portal alerts
    • Show damage reports you sent total and for the last month
    • Ability to set portal selections on Intel map based on an existing Portal Group
    • Variable distance setting for Agent/Portal default views
    • Home portal system
    • Ability for top tier users to assign faction claims/home portals to other users on their faction
    • Ability to set coverage and color for agent portal alerts
    • Need to add self-flipped portal alerts
    • Portal notes system not built
    • Agent notes system not built - maybe gonna nix this... could see this being abused (like people putting people's home address)
    • Portal Claim system not built
    • Global Leaderboard
    • Log Agent's level
    • Allow agents to flag a portal as a portal they tend to have keys for (for agents looking to use something as an anchor for an op)
    • Build alert destination system
    • Allow portal selection to be circle or rectangle shape
    • Auto-complete agent names when creating agent alerts
    • Double clicking Draw button "sticks" it on (for power users)
    • Double-clicking geolocate button makes map center follow you
    • Build system to coordinate key exchanges
    • Look at maybe doing event based microdata
    • Ability to link to a portal on intel map
    • Build portal group system
    • Ability to assign priority to Portal Groups
    • Send "welcome" email to users once their first damage report comes in (once we know which faction they are)
    • Remove minZoom when viewing agent's area of play
    • Show attacks by hour on portal page
    • Ability for admin to merge agent data (in-game name change)
    • Portal selection system
    • Show map on portal page
    • Allow dismissal of portals listed on agent's "Last Known Attacker" tab
    • Option to see portals you've never sent a damage report from
    • Options to show agents that tend to play in a certain area - maybe not super useful now that I think about it... based on damage reports, and some areas that never get taken (like Poway) probably wouldn't even show those people as playing there since no one ever really takes those portals
    • Multi-select/deselect tool for portal selections
    • Tools tab
      • Simple hack mod calculator
      • Link distance mod calculator
      • Mural mission icon slicer
    • Tool that can calculate optimal linking pattern between a selection of portals
    • Slack slash commands for querying agents and portal info
    • Push notifications once Chrome support payload data (see this Chromium bug)
    • Build a custom mail transport that is multi-theaded - handle outgoing emails, handle incoming emails, exponential back off when outgoing emails exceed allowed rate (deferred?), setting for number of concurrent threads, graceful fallback to single-thread, process that handles incoming emails turned into a daemon with angel process
    • Build system that allows servers to be proactively notified when a new damage report comes in
    • Replace default Google Maps marker icon for portals
    • Have toggle to show claimed/unclaimed portals
    • Normalize addresses
    • Avatars and attachments need to be stored in database rather than file system
    • Handle incoming damage reports where a portal has no picture
    • Make a fallback generic image for portals with no picture
    • Reformat latest portal/agent activity tables
    • Friendly fire opt-out system to suppress reporting friendly fire from own faction
      • Make it so effect of setting can be changed once a week vs. setting itself
      • Suppress friendly fire data from:
        • Intel map
        • Agent area of play
        • Portal profile
        • Agent profile
        • Portal ADA/Jarvis tabs
        • Users who have not sent a friendly fire damage report email recently (soft-opt out for users suppressing them on their end)
    • Show days since last recorded attack on a portal (easier to see number than calculate in head)
    • Show first 3 letters of agent name instead of 1 on the alert marker for agent
    • Intel map making unnecessary position change callback for each alert upon initial page load
    • Start logging links being destroyed
    • Create tool that rebuilds links that have been recently destroyed by a specific agent
    • Proxy portal images (forces them to be on SSL and can also serve up via global CDN)
    • Load agent profiles via AJAX overlay when on intel map
    • Optimize size of heatmap underlying data (less data transfer is always good)
    • Search function for portals
    • Search function for agents
    • Show general global stats
    • Include both factions in attack summary on portal popup on Intel
    • Portal Intel popup should be able to set Key/Claim flags
    • Calculate bounds and center point for broken links and use that when showing map of links recently broken
    • Do DKIM & SPF validation on incoming emails to make sure they only originate from Niantic (prevent email spoofing by people trying to inject false data)
    • Build system that allow faster querying of a massive amount of spatial data - holy crap it's fast
      • Migrate damage reports
      • Migrate portals
      • Migrate agents
    • Throw order/distance management system for large ops
    • Don't initialize agent's "Area of Play" map until that tab is selected
    • Look at what we could do with Google's machine learning system they recently open sourced: TensorFlow
    Permissions
    • Allow agent who is feeding data to see everything we know about themselves (basically give them premium member access when viewing themselves)
     
    Last edited: Mar 4, 2016