I'm pretty sure that since a month or so, SEDE seems much more eager to get rid of my session and log me out in that process.
I don't mind logging in a couple of times per day, if that helps to reduce resource consumption, but the user experience isn't all that great when it happens.
Here is why: I'm most often in the middle of writing a query for an MSE question, for example this one. So I have the edit window open and am creating a new revision of my query. When I click "run," I do notice the button gets grayed-out, as it normally does, but I never get any result back. There is also no error message.
To recover from this I have to copy the SQL text I have typed, open a new tab and load SEDE, log in, switch back to the stalled tab, refresh, paste the SQL text, run query. Repeat the process after 10 minutes.
If the intended behavior is to log users out of their session on such short notice (I recall sessions lived for 24 hours), can there then be a slightly better handling in the browser of that state, so it is clear you're logged out once you click the run button?
I prefer, however, to have the longer allowed sessions back.
I'm experiencing this behavior mostly in Chrome on Win 10.