oh that’s fucking weird. it might have something to do with how bonkers lemmy’s session handling is

I’m planning an update to the latest Lemmy release fairly soon; usually I hold off on updates a bit because new Lemmy releases tend to have horrific bugs that nobody seems to talk about [1], but we’re nearing the time when an update makes sense. we should check after that update if it fixes this bug; if not, it’s one of the things we can fix in our fork.

[1] but the admin of a large instance sure as fuck will come here and link lemmy’s worthless docs to say the problem is mine, and when I look I find out their instance had the same fucking issue but they were too big to notice a bunch of their userbase was broken