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
The official Kilter app uses the same session token for a long time. I've been playing around with it for over a week and it has never requested a new session.
BoardLib creates a new session everytime it runs.
Should we end the session after we got all wanted information from the server so it doesn't have to store so many useless sessions?
Sure, for the logbook command this seems like a reasonable minor improvement. Perhaps the bigger improvement here would be to have the option to stash tokens somewhere, so that the login could be skipped. For Climbdex, I store these as cookies. For command-line usage, perhaps a file somewhere which maps username + board name to last session token.
The official Kilter app uses the same session token for a long time. I've been playing around with it for over a week and it has never requested a new session.
BoardLib creates a new session everytime it runs.
Should we end the session after we got all wanted information from the server so it doesn't have to store so many useless sessions?
The API call looks like this:
The text was updated successfully, but these errors were encountered: