So, the short answer is that most things on this website are entirely based upon what the defaults were, and no one has volunteered to upgrade/migrate content.

The longer answer as to why the defaults are as such would be that the website *only* maintains a session cookie, not an auth token. So, if the session is expired, you have to log back in.

Why would sessions be expired? Well, most likely to avoid accumulating them endlessly over time and allow garbage collection to run. There's presumably minor security benefits as well, if people abandon a machine.

One trivial thing I *could* slap in would be a setInterval() ping of the website every few hours or so, so that if you left the web page open it would be considered an active session... Hopefully this would not be a tremendous amount of load on a currently volunteer hosted website...

Is logging in such a hassle though? Surely you can just let your browser password manager or external password manager autofill?

I do have autofill, but the website isn't very friendly on mobile. Also I'm used to being logged in everywhere >_>

Hm, certainly true this ancient design has never been updated for mobile. It might be possible to tweak that a bit w/ some simple style changes...

Not to sure what that has to do with logging in though ☺

Anyway, if you want to volunteer to help upgrade us, main issue is data migration.

unc0rr made a sanitised set a while back for someone to use as a target for their scripts.