supakaity

joined 2 years ago
MODERATOR OF
[–] supakaity@lemmy.blahaj.zone 1 points 2 years ago (1 children)

It seems like it is an identified issue with token invalidation in lemmy and they will be fixing (or have already fixed?) it in a future upgrade.

I'll keep an eye out for it and try to get it in as soon as possible. In the meantime, clearing site cookies while tricky is the only real option.

[–] supakaity@lemmy.blahaj.zone 5 points 2 years ago (1 children)

We will be going to 0.18.2

[–] supakaity@lemmy.blahaj.zone 28 points 2 years ago

Migration complete.

[–] supakaity@lemmy.blahaj.zone 2 points 2 years ago (3 children)

Not sure.

Some people have had to clear cookies to get things working again properly.

Are you getting an error message in the javascript console?

[–] supakaity@lemmy.blahaj.zone 2 points 2 years ago* (last edited 2 years ago)

Should be fixed (again) now, I gave it a kickin' and it decided to work.

[–] supakaity@lemmy.blahaj.zone 2 points 2 years ago

Should be fixed now

[–] supakaity@lemmy.blahaj.zone 2 points 2 years ago

Should be fixed now.

[–] supakaity@lemmy.blahaj.zone 6 points 2 years ago

Not sure what was wrong, there was plenty of space on the drive (27GB available). Restarted pict-rs service and it is all working again.

[–] supakaity@lemmy.blahaj.zone 5 points 2 years ago (1 children)

I love the final state: "success"

Is there anything better than a successful error?

[–] supakaity@lemmy.blahaj.zone 1 points 2 years ago* (last edited 2 years ago)

Well, I don't technically work on the lemmy codebase (I have my hands full with adminning 3 instances and working on Hajkey), but yes I agree it'd be nice if the lemmy dev team could spend some time reviewing and improving the security, in amongst all the other stuff they have to do since Reddit imploded.

[–] supakaity@lemmy.blahaj.zone 2 points 2 years ago

It wasn't an actual emojo. The script processed the SQL header column names as an emojo and tried to add them. Unfortunately publicUrl is not a valid URL, so lemmy's /api/v3/site metadata endpoint started returning an error relative URL without a base instead of the JSON that the website was expecting and so the site just stopped working for everyone the next time it tried to load that url.

[–] supakaity@lemmy.blahaj.zone 0 points 2 years ago* (last edited 2 years ago) (2 children)
view more: ‹ prev next ›