EDIT 10:33am EST: all clear! thanks for using cohost
happy sunday everyone
you have likely noticed that you are getting logged out of cohost more frequently than you would expect. we are once again hitting limits with our session storage, so sessions are getting expired more quickly than they should.
we are bumping that DB to another level and, while it's ostensibly a zero-downtime process, there will likely be a few minutes of downtime. we'll sound an all-clear once it's done.
Had the exact issue this morning, logged in to see this at the top of my feed. Well played, eggbug
I just assumed you were trying to get me to check cohost less often, which I of course rejected whole heartedly.
Ooh you're storing sessions in the database?? Damn hell yeah. Last time I was looking at session management everyone was like "JWT JWT JWT JWT" and tbh I don't quite understand the hype. It's a signed cookie, and it doesn't provide any mechanism for forced sign-outs, which seems like a necessary feature.
I don't know about JWT specifically but the general idea does allow for forced sign-outs: Just store the forced sign-out people instead of the signed in ones. Best of both worlds.
That's true, it's way fewer sessions to store. It just seemed like I was gonna have to build out tracking sessions on the DB either way, with a lookup on each request, so from a lazy developer perspective there wasn't an advantage :P
i didn't notice as i was not using the computer at that time. good work
This does seem to have addressed the issue for me, I haven't been logged out since this post, but other users are still reporting issues: https://pony.social/@thephd/109421531065705660
I think this update reset the "quick share on mobile" setting back to On for me. Was that intentional?
