LB-641 suggests a way of allowing users to specify their timezone so that listens can be converted into the correct timezone when displayed to the user.

however, this doesn't work in all cases, especially when someone is travelling.

A solution to this would be to allow clients to submit the local time in addition to the listened_at timestamp. Unfortunately our schema doesn't quite support this. I had hoped that it could go in additional_info, but is this really "track_metadata"? Does it matter?

{
  "listened_at": 1443521965,
  "track_metadata": {
    "additional_info": {
      "listened_at_local": "2015-09-29T03:19:25-07:00",
      "release_mbid": "bf9e91ea-8029-4a04-a26a-224e00a83266",
    },
    "artist_name": "Rick Astley",
    "track_name": "Never Gonna Give You Up",
    "release_name": "Whenever you need somebody"
  }
}