Johan von Forstner

> Thanks for your contribution! So which one would you prefer? Use the desktop version and live with the session expiries? Or put more work into the mobile version? Or...

New observation about the desktop API: `queryMoreTrips` works *sometimes*, but not always... I just ran the test 100 times, and out of those, it successfully requested later and earlier trips...

Yeah, seems to be exactly that - when the `queryMoreTrips` request succeeds, the `Server` HTTP header is the same as in the initial response, and when it fails, it's a...

I sent an email to the MVV to ask if this can be changed - in principle the server name is already included in the `sessionID`, so it should be...

Okay, that sounds like a good interface for the methods of the new mobile API. Yes, exactly, it seems that it is logically identical except for the tag names. But...

Yeah, with the new mobile API it's exactly the same problem - if the server responding to the followup request is not the same as for the initial request it...

MVV seems to not be helpful in this regard - probably you would first need to ask them for an official permission to use their data: > vielen Dank für...

Hi @schildbach, I have implemented a workaround to make queryMoreTrips work with the new API despite the load balancer in 72ef473. Instead of using the session-based `tripNext` command, it simply...

@alexander-albers Thanks, this looks good! @schildbach, have you had time to take look at the updated PR so far? If you want, I could also implement this workaround as an...

Maybe this is the same problem as in PyCharm, see #62 and #89. A workaround seems to be to add the following: ```python from fastprogress import fastprogress fastprogress.printing = lambda:...