always exit app when map is focused and back button is pressed (fix for #650)
sort artifact list by shard number, then by target portals
ensure we don't break for artifacts without jarvis data (e.g. a future artifact type)
make shard marker semi-transparent - avoids the harsh white outline and makes the underlying portal and it's colour partly visible
geodesic lines: improve the handling for lines that extend beyond the antimeridian. no odd straight line segments
leaflet doesn't have particularly great handling for this, but this is a reasonable measure for now
leaflet 0.7 release
hopefully improves things further, especially on kitkat
Fix a couple of typos.
Merge pull request #653 from nexushoratio/to-push

Fix a couple of typos.
basemap cleanups
- updated Google, Bing and Yandex externals from https://github.com/shramov/leaflet-plugins
- also renamed Google file, removed internal hacks for INGRESS map type
- used external included file for Bing maps, instead of embedded in the plugin
- used Google map tile API to set the options for the INGRESS and 'Google Grey' map layers
cache bing maps metadata - without this likely to exceed free quota for map tiles
Spell checking, a-c.
Merge pull request #654 from nexushoratio/to-push

Spell checking, a-c.
Spell checking, d-g.
Merge remote-tracking branch 'upstream/master' into to-push
getAvgResDist - return a small, but non-zero, value for zero distance resonator deployments (zero is already assumed to be no resonators deployed)
portal-highlighter-bad-deployment-distance: highlight colour based on resonatror range: purple: likely 0m deployment (spoofer?), red <10m, orange under 24m, yellow under 36m otherwise no highlight
Merge branch 'master' of https://github.com/jonatkins/ingress-intel-total-conversion
Merge pull request #655 from nexushoratio/to-push

Spell checking, d-g.
request munging: call the stock site nemesis.dashboard.requests.normalizeParamCount function, to add in dummy parameters to requests
for #656 number 1
limit the number of player names resolved in one go, to prevent excessive requests
for #656 number 4
COMM: correctly use the ascendingTimestampOrder flag when retrieving new COMM messages. this matches the stock intel site, and prevents gaps occuring when filling in entries after resuming from idle
related to #656 no 2
reduce the number of 'all' comm messages retrieved in one go to 50 at a time
related to #656 no 2