hah, this is fantastic. Good on you Ruud

I’ve discovered a pattern to my logout error as referred to here: https://lemmy.world/comment/1144382

It occurs specifically when I navigate to a community page, without visiting the homepage first. If I navigate specifically to, for example, lemmy.world/c/lemmyworld, I’ll be logged out. However, if I visit lemmy.world and then visit lemmy.world/c/lemmyworld, I’ll be logged in.

I wonder if this is a bug with SameSite in the JWT? Reddit’s token, for example, has a value of None, where Lemmy’s has a value of Strict. I’ve changed that to None for the moment, we’ll see if that changes anything

Holy shit this looks practically perfect. Thanks!

On opening a new tab or window with a lemmy instance, I frequently find that I am not intially logged in. I am logged in, and refreshing the page a few times affirms this. It does not necessarily require a cacheless refresh (ctrl+f5). It also occurs regardless of what lemmy instance I’m browsing.

This started immediately after the hackening event of the other day. I’ll play with what’s in site storage in firefox later on and see what happens.

Edit: Ok something very odd just happened. I did the refresh thing and it briefly showed me logged in as @andybug@lemmy.world, for reasons unknown. It didn’t stay logged in as (s)he, but very briefly flashed it as such.

Edit2: I deleted cache, webtoken, and other detritus in firefox, and refreshed the page to login again. I logged in, and the site served me the logged-out homepage until I refreshed again. ¯_(ツ)_/¯

Edit3: I was logged out completely this morning. No explanation as to why as yet, I’ll test tomorrow and see what browser storage looks like