You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a point on the live map (/last) is clicked on, we see the user card with face and name:
when the next live location for this user arrives at the map, only the tid is displayed and no longer the name, probably because we haven't stored CARDs in local storage which we likely should.
And while we're at it, the whole styling of the popup could do with quite a bit of refresh.
The text was updated successfully, but these errors were encountered:
When processing the most recent location update this gets pushed over the
websocket to update the live map last position. If a card is present it
needs to be added just before this push occurs.
- FIX: add card data to websocket notifications (#450)
- FIX: Enable building when WITH_TZ=no to disable timezone information (#473)
- FIX: view lastpos response (#471)
- FIX: handle out-of-order location notification in last/ (#472)
- FIX: drastically reduce memory leakage in views (#464)
- FIX: reformat json if it contains newlines/tabs before storing in .rec (#437)
- NEW: cached geo records can be auto-expired by setting OTR_CLEAN_AGE (#447)
- NEW: option -J prints variables in JSON format, for scripting
- NEW: version is printed in -J / -V
- FIX: in http mode friends' data must contain a topic; construct it or retrieve from last if available (#451)
- FIX: crash on non-string event name in _transition messages (#454)
- NEW: Add alt field to GeoJSON points parameters (#456)
When a point on the live map (
/last
) is clicked on, we see the user card withface
andname
:when the next live location for this user arrives at the map, only the
tid
is displayed and no longer thename
, probably because we haven't stored CARDs in local storage which we likely should.And while we're at it, the whole styling of the popup could do with quite a bit of refresh.
The text was updated successfully, but these errors were encountered: