One way we can justify relying on somewhat magical heuristics is when developers can opt-out of them by following our guidance. I.e. we provide a rational alternative for the API which by default behaves somewhat magically. Along these lines, should we consider adding an additional argument to setTimeout that indicates the scheduling policy, eg. "interactive" or "best effort". Then the default when unspecified ("auto") can use whatever heuristic we find best balances web

https://cdn.freeriderhd.com/free_rider_hd/assets/images/icons/dialog_button_icons_v6.png

processGoogleToken({"newToken":"AHva7osi2EblxeAA3HUrYcc1uvrWedvpZ1XsvhYDFM0bfTlgxxHzDX0M5w","validLifetimeSecs":300,"freshLifetimeSecs":300,"1p_jar":"","pucrd":"Cg8IABABGAMgACgAOAGIAQF4Aw"})

processGoogleToken({"newToken":"AHva7oshZet8x8K4C59g2UQ__EUAw6g_Uooj1FVTPFoya5bYdilPVN45kg","validLifetimeSecs":300,"freshLifetimeSecs":300,"1p_jar":"2018-9-29-16","pucrd":"Cg8IABABGAMgACgAOAGIAQF4Aw"});