botffy / timeline.fm Goto Github PK

Multiple travel segments are by default displayed squashed together. That can be opened to see the actual travel segments, with the music information correctly shown.

But when the multitravel segment is not opened down, there's no indication you've listened to music during that time. Inserted Google Photos work the same way, but I sort of feel we'd need to show at least something.

Related to #2

The list of scrobbles is public only if the user didn't check the "Hide recent listening information" checkbox in the Privacy tab in Last.fm settings. Worse, the error is never reported due to #2 .

It's be better to actually authenticate the user.

If you load https://www.google.com/maps/timeline, then navigate to any day, the scrobbles won't load for that day. Works fine later when we navigate to another day.

Apparently we catch the creation single-day-element, but that changeset includes the creation of the segments as well. So even though we create the main listener, that listener doesn't catch the creation of the segments (as those are already created).

The extension currently assumes all times on the Timeline page are in the same time zone as the computer running the browser. If you've ever traveled outside your current time zone, that's not the case.

This is tricky, since there's no time zone or geo information in the DOM, so we can't actually determine the time zone of an activity.

A possible solution might be to fetch the original JSON about the location information, and consult that while parsing the DOM.

No time information is displayed for unknown activities, causing the script to crash.

We always assume the end time of the last activity is 23:59 of the day of the last activity. This is incorrect if the last activity already ends on the next day. In that case the end time of the last activity should equal the start time, I think. Maybe we could be less exact and make it start time + 1 hours or something

No error is displayed if the scrobbles could not be loaded for whatever reason

It can be fixed fairly easily, but do we really need this?