You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
timeclonk logs us out pretty regularly. I had increased the token timeout, but its still not fixed.
thinking about making a new token every site visit, replacing the old one, and never requiring login after the first time. better than a permanent token. anyway needs fixing.
The text was updated successfully, but these errors were encountered:
In the current scheme a new token is created on page load, and the previous token is expired. But the problem is sometimes the new token doesn't get set in the browser, and the previous token keeps being used. The result is a new login being required.
Tentative solution is to create a new token on page load, and link it to the previous token. When the new token actually gets used by the browser (ie api call), then the previous token will be removed. I'll experiment with this on zknotes before trying it here.
timeclonk logs us out pretty regularly. I had increased the token timeout, but its still not fixed.
thinking about making a new token every site visit, replacing the old one, and never requiring login after the first time. better than a permanent token. anyway needs fixing.
The text was updated successfully, but these errors were encountered: