[17:40:34] I still seem to be logged out a lot [21:38:01] Reedy: yeah, something is definitely going on. T383566 is the (a?) task about it. [21:38:02] T383566: Some editors are frequently getting logged out (multiple times a day) - https://phabricator.wikimedia.org/T383566 [21:38:17] Aha, good it's not just me [21:38:24] I'd seen the old task was closed, and was a little confused [21:38:25] if you are willing to investigate, some of the information that tends to be useful: [21:38:45] - do you need to log in, or does autologin work, just needed more often than normal? [21:39:16] - does it affect the same wiki where you logged in (filled out the login form), or just the other top-level domains? [21:39:28] I have to login to at least one wiki, then the autologin seems to work elsewhere [21:39:43] I'm not 100% sure, but I seem to be logged out basically every day [21:40:07] Not so much when I'm using it, it's more like "I wake up in the morning and am logged out" [21:40:08] - do you have login cookies (there should be three centralauth_* cookies and five * cookies), with one year expiry for most of them? [21:41:19] I don't seem to see 3 CA cookies [21:41:27] _User and _Session I do see [21:41:56] _User is a month away [21:42:03] _Session has none [21:42:04] so that means no "keep me logged in" flag [21:42:23] Annoyingly, 1Password has started pressing the log in button for you [21:42:35] So you autocomplete... And then it's logging you in before you can check it [21:42:40] Changing the muscle memory workflow to check it first... [21:42:45] and in practice ~24 hour session expiry since that's the central session store retention time [21:44:18] if you are sure you checked the checkbox, the next question would be, do you see this on the domain where you logged in (which would be an AuthManager bug) or only on other domains (that would mean autologin not copying the "keep me logged in" flag correctly)? [21:44:58] I will note it seems to be (a lot lot?) worse on FF [21:45:08] I have my WMF account on Chrome, and that seems to stay logged in for much longer periods [21:46:38] That's potentially a third thing: some browsers will forcibly reduce cookie lifetimes when they decide the login flow resembled user tracking. Not sure if/how that shows up in the developer console. [21:47:22] Hopefully SUL3 will help with that, though hard to say for sure. [21:48:50] You can set a per-site exemption from third-party cookie blocking: https://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection#w_enable-third-party-cookies-for-specific-sites [21:50:14] technically third-party cookie blocking and what I suspect is happening here (bounce tracking mitigation) are different things, not sure if FF Enhanced Tracking Prevention includes both, but worth a try [21:53:52] if you want to investigate the relevant FF doc is https://firefox-source-docs.mozilla.org/toolkit/components/antitracking/anti-tracking/bounce-tracking-protection/index.html#list-recently-purged-sites [21:54:03] though I have no idea if it's accurate