now we no longer can reconstruct missing short links from the portal data, and the backend servers already cull short links from the data, there's no point in skipping display of short links
remove portal clustering code, that preventing all portals we get data for being drawn to the map
this was an optimisation, as leaflet can be slow when drawing a lot. however, as the backend now limits the data returned to the browser this is less important and probably wastes more time than it saves
for #774
simplify map data request batching - doesn't need to be so complex now we never request more than 4 tiles per request
cache expiry time was 2 mins, but default intel site uses 3 minutes - mis-read their timer value
revert ea45d0f447af24115275234403202fe993e0d84c - portal clustering still has some advantages
note: window.Render.prototype.getLinkPixelLength not restored - should have been deleted as part of an earlier change
portal-names - use different delays for data loading updates and user events - improves performance
test: remove code that rendered stale map data tiles from cache before retrieving from the network - will try it for a while and see if it makes things noticably more responsive
update munge regular expressions for changes 2014-02-22
note: request format for map data has also changed and code needs updating
protocol changes 2014-02-22 - quadkeys have gone back to using map zoom, rather than portal level, in their names
temp disable show more portals and default intel detail plugins - the code changes needed for protocol changes have broken them, and i need a bit of time to study the details before fixing them
bump version number for new release
update plugin descriptions from "PLUGIN CURRENTLY UNAVAILABLE" to something more descriptive. Hopefully will reduce questions in the community concerning these ones