Added new cone prediction (95% confidence interval) and removed old AR predictor.
Remove dead logging.
add fade out effect to predictions

As time from last known, increases, the confidence aka opacity, decreases.  By
11 minutes, the prediction starts to aggresively deviate towards means in ways
that are not believable, as Adrien de Croy points out.  This makes the
prediction start to fade out by 12 minutes in.  By 30 minutes out, the
prediction is invisible, and requires straining to see after 15 minutes.
Change time deltas.
Added new cone prediction (95% confidence interval) to websocket.js predictor and sent to client.
Merge remote-tracking branch 'origin/feature/confidence-interval' into feature/confidence-interval
Increased prediction horizon to 65 minutes.
Changed futureOpacity to range to 65 minutes, same as prediction horizon
Added kludge, see TODO note.
Removed predictedCI from websocket.js.
Made now focus predictor on client instead of server since using confidence interval.
Removed retrospectivePredictor boolean (now always on) and basic cleanup.
Removed dead code.
Added to TODO note, so that updating is clear.
force predictor to fade out a bit more
v0.3.3
merged develop into feature/confidence-interval and fixed conflict in bower.json
upsert instead of insert to prevent exact dupes
don't forget the upsert option
callback expects an array