this post was submitted on 28 Jul 2023
169 points (100.0% liked)
/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 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I didn't have this issue at all yet, very rarely I do get logged out without me doing anything but that happens only while I am not using kbin at all so I just have to log back in and nothing is lost.
Errors while upvoting posts I do sometimes get and I'm thinking that the problem is that I'm upvoting something at exactly the same time someone else is. It leads me to an error page, I click the back button to get back to the post, reload the page and upvote again and it works.
But I never got sent to a login page as an error.
The error page I get sent to just says "Error" but the tab's name is "Log in", personally. That's why I assume it's some kind of log in issue.
This might actually be a helpful detail for @Ernest. Come to think of it I think I'd noticed this too, but when you hit back you are still logged in.
I'm using mobile, so don't see the tab name, but my name is replaced with 'login' from what I remember. I'll screenshot and edit this comment next time it happens.
Edit: ok I was wrong. On mobile it does still show my Avatar, not the 'login' text on the generic "Error" page.
Maybe. I just never really looked at the tabs name and just hit back 🤷. I was never logged out though so either we had different errors or it really was just an assumption on your side.
I'd need to re-encounter my error to check, but now that I want to re-encounter it, it won't ever happen again.
Edit: Actually ☝️🤓, I literally JUST re-encountered it, the page did indeed say "Log in" but I was still logged in and my profile picture etc still showed up in the upper right as usual.
I get the same thing, and far more often with larger threads
Yes it seems like in those instances, maybe the page hasn't finished loading completely, and waiting a little bit before retrying the action fixes it.