/kbin meta

4 readers

1 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

169

Kbin's "Log in" bug is discouraging me from participating (kbin.social)

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

48 comments fedilink hide all child comments

Every time I try to upvote or boost something, there's a solid 20% chance it'll link to an Error page titled "Log in". That percentage seems to increase the longer I've had my Kbin tab open without refreshing it.

Even more annoyingly, it regularily logs me off completely, forcing me to input my information again. It's especially annoying on mobile since it won't even remember my password for some reason, which was randomly generated, meaning it's a pain to re-enter it every time.

The effect is that it's making me interact with Kbin less and less, I end up just scrolling without upvoting or commenting or anything, and ultimately I also just use the site less overall.

I like it here otherwise, but this one bug is making Kbin a real chore to use, and I know a lot more people have been experiencing it for a while now.

you are viewing a single comment's thread
view the rest of the comments

[–] ernest@kbin.social 130 points 1 year ago* (last edited 1 year ago) (12 children)

Ok, so in the next few days, I'll be testing some things. It might be a bit worse for a while, but it will definitely speed up the problem-solving process. I'll be grateful for any feedback. I'm unable to reproduce it in local/testing environments, so it might be an issue with the cluster.

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

Apparently, the error condition might NOT be dependent on idle time (a period of time without any interaction). — Evidence: Periodic clicks on a vote button, scripted at 45-second intervals, did not prevent the error's eventual occurrence.

load more comments (11 replies)