| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Google really is picky about these … and does not even seem willing to
tell which thresholds it uses …
|
|
|
|
now takes all potential stops along each trip into account when guessing
tickets; also checks if a ticket is still likely in case the tracker
switched its direction. This should solve many cases where a tracker is
accidentally turned off or falls asleep halfway before the last station
of one trip, then wakes up in the middle of the next.
|
|
there's some trade-offs here (cookies may be discarded by the browser,
query parameters lost if people use a bookmark), but either works fine
for not re-issuing tokens if someone reloads the web site.
|
|
|
|
largely based on things noticed on 2024-05-01, this year's first day
of Ilztalbahn trains running.
|
|
this is mostly meant to guard against the gtfs changing under
tracktrain, and not yet complete (e.g. a ticket does not yet save its
expected stops, which it probably should).
|
|
|
|
most of it deals with timezones, and all the weird implications that has
|
|
|
|
|
|
(tough mostly untested)
|
|
|
|
(kinda barebones, but the important things should be there)
|
|
|
