/kbin meta

16 readers

2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

kbin Login bug fixed? (kbin.social)

submitted 1 year ago by Varyag@kbin.social to c/kbinMeta@kbin.social

8 comments fedilink hide all child comments

I haven't used kbin much this past week, but over the last day or so I noticed I haven't seen the "login bug" happen anymore. I can leave a tab open and still come back later and upvote, boost or comment on posts without the page giving me an error and asking me to re-log in.
So, I don't know what our guy ernest did, but let's give him some recognition and appreciation for actually fixing it! At least for me, it seems fixed. Anyone else noticed it?

top 8 comments

sorted by: hot top controversial new old

[–] wagesj45@kbin.social 8 points 1 year ago

There was a pull request that got approved a bit back. Seems like it was published because I haven't seen the issue here for several days.

[–] HidingCat@kbin.social 7 points 1 year ago

Yea, same, looks like that bug is gone. Hooray!

[–] ninbreaker@kbin.social 2 points 1 year ago

Still broken

[–] VulcanSphere@kbin.social 2 points 1 year ago

Can confirm, it's gone, yay!

[–] gentleman@kbin.social 1 points 1 year ago

@Varyag Same for me. Looks like it’s fixed

[–] Sarsaparilla@kbin.social 1 points 1 year ago* (last edited 1 year ago)

Yeh yeh I think it's good!

edit: absolutely! I just had this thread sitting open in a tab for about twenty mins before commenting. Thanx @ernest !! ❤️

[–] vrwarp@kbin.social 1 points 1 year ago

I use Chrome on Android and it continues to run into invalid csrf token even when the cache is cleared. This usually resolves itself in a few days.

[–] NikkiNikkiNikki@kbin.social 1 points 1 year ago

I also haven't had the issue, or the problem where upvoting in the feed goes to an error screen, might've been related?