I am not extremely clear if this is a purely client concern vs a server-side concern, but right now I don't think there's a token refresh logic built into the client, and this means that (apparently) very long sessions with owl-control are generating bad auth and people are having to log back in. Ideally we'd refresh in the background as long as the user was still logged on, subject to maybe some timeout for force logging them out if idle.
Because this overlaps a lot with the concerns we'd have and what we'd have to write for #180 it might make sense to simply do this as a quality of life improvement along with that.
I am not extremely clear if this is a purely client concern vs a server-side concern, but right now I don't think there's a token refresh logic built into the client, and this means that (apparently) very long sessions with owl-control are generating bad auth and people are having to log back in. Ideally we'd refresh in the background as long as the user was still logged on, subject to maybe some timeout for force logging them out if idle.
Because this overlaps a lot with the concerns we'd have and what we'd have to write for #180 it might make sense to simply do this as a quality of life improvement along with that.