search

iitc-project / ingress-intel-total-conversion

ingress.com/intel total conversion user script with some new features. Should allow easier extension of the intel map.
http://iitc.jonatkins.com/
ISC License
991 stars 552 forks source link

COMMS data is significantly outdated #902

Open joshsweaney opened 9 years ago

joshsweaney commented 9 years ago

I've noticed that the data retrieved in the COMMS panel is usually significantly behind the current time, especially when the page is left idle for more than a couple of minutes. Why isn't the latest data fetched from the server? Is this a problem with IITC, or on Niantic' end?

Is there a way to force more COMMS data to be fetched at once so that it can be kept up to date? Out-dated info makes using the player-tracker plugins quite difficult, and is also annoying when you are trying to use it for basic communication.

jonatkins commented 9 years ago

This is currently working as intended - and, I believe, matches the stock site behaviour for COMM.

If IITC just pulled the most recent 50 entries on resume (rather than the oldest 50 since last retrieval) , it would have to throw away any current scroll-back buffer otherwise it would end up with holes in the history.

Personally I find the current behaviour useful, particularly combined with the auto-update feature of the 'uniques' plugin - open the desktop map when planning on what to do, go out and attack/link/whatever, then come back and let COMM download for the entire time you were out.

There are two things you can currently do to get the latest COMM data faster

  1. scroll back a small amount, then return to the bottom - e.g. using the mouse scroll wheel. This will make IITC fetch the next 50 COMM entries. Repeat as needed...
  2. pan/zoom the map. If you zoom, or if you pan more than a small amount (approx 10% difference in view), IITC will forget all COMM history and download the latest COMM messages only

This is an area that could be done better - but a lot of the COMM code needs work...

joshsweaney commented 9 years ago

Ah I see. Yes, the behaviour is certainly useful so that you can see full COMM history. What I wish it would do slightly differently, is upon resume it would download all past history up to the present, that way you wouldn't need to download 50 messages at a time, or refresh the page and loose most of it.

Yes, the COMM code needs a huge amount of work. Unfortunately, there's not much that can be done within the bounds of Niantic's protocols, and trying to keep as within the TOS as possible for a third party modification.

nhamer commented 7 years ago

Can this issue be closed? It can't be changed without presenting a significant change in access vs stock.