@prologic@twtxt.net I do NOT claim to be an expert in that realm. I’ve seen different things being implemented in the guise of “remember me”. But I reckon the most common scheme, when this checkbox is activated, is to issue a dedicated, long-lived refresh token in a login cookie. I’m sure it is known under several different names. This “remember me” login cookie is separate from the actual short-lived session cookie.
Part 2 of this answer explains it fairly well: https://stackoverflow.com/a/477578 Also, this was a nice read: https://web.archive.org/web/20180819014446/http://jaspan.com/improved_persistent_login_cookie_best_practice
It depends on your threat model, but the use of public computers in libraries, internet cafés or similar is probably the most relevant here, when arguing against activating “remember me”. These days, shared computer use is declining I’d assume. With twtxt being a niche for more computer-affine folks, I’d reckon this threat is not that high up the list. On the hand, you want to bring yarnd to the average non-nerd user, so this threat might actually rank more important.
It’s probably okay and safe enough to remove “remember me” entirely and just issue a long-lived session cookie and be done with that. Optionally, power users or the administrator could benefit from configurable cookie lifetime(s).