Sometimes kbin will ask me to login again but I just refresh and it’ll show me logged in, I think it’s a federation issue if people haven’t interacted with the post or something?
Other times it’ll ask me to login and return a CSRF token error and if I refresh it again, it’ll fix it.
Minor bugs, everything has mostly been pretty smooth. Just using a shortcut on my homescreen, no apps or anything.
Yes, refreshing solves it - despite it being called the “login bug”, you do not actually have to log in again - thanks for making sure that people know:-). It seems that after some time - a minute? - has passed, it has already forgotten who you are, and it needs to be reminded again. But it’s annoying b/c who reads a post, all the comments on it, and writes out a response, all in under one minute!? (on a mobile screen no less, with those keyboards) And if you write a second comment, it will happen again. And again, and again, forever - at least it is predictable:-P.
The Notifications issue is pretty debilitating though - you must have managed to avoid ever running afoul of it (it does seem fairly rare), but it blocks your ENTIRE Notifications, from EVERYONE, from every instance, every post, every comment you’ve ever done, and permanently increases your Notification count, which can never be viewed and thus never go back down to zero. I even tried going back through every post and comment that I have ever made in the last several months, but I still have a “1” there that I cannot ever view (b/c once the moderator of another instance removes it - which btw Kbin lacks any moderation tools at all iirc - you cannot view the post anymore, hence you cannot view the comment of the person who replied to you, hence it is “unread”… forever). Eventually the situation that causes the error message will fall behind and you can view the newest page of results (but not the entire page on which the original comment occurs), but then the whole thing can happen again, and again, and again, each time burning your entire Notifications system all over again.
Not being able to receive Notifications almost defeats the point of a social media site?! And unlike the former issue, the latter still applies when accessing from a desktop computer. So I would not call that one a “minor” bug - it is more like a rarely occurring major one. I am glad that your own experience has been smoother than mine though:-).
Sometimes kbin will ask me to login again but I just refresh and it’ll show me logged in, I think it’s a federation issue if people haven’t interacted with the post or something?
Other times it’ll ask me to login and return a CSRF token error and if I refresh it again, it’ll fix it.
Minor bugs, everything has mostly been pretty smooth. Just using a shortcut on my homescreen, no apps or anything.
Yes, refreshing solves it - despite it being called the “login bug”, you do not actually have to log in again - thanks for making sure that people know:-). It seems that after some time - a minute? - has passed, it has already forgotten who you are, and it needs to be reminded again. But it’s annoying b/c who reads a post, all the comments on it, and writes out a response, all in under one minute!? (on a mobile screen no less, with those keyboards) And if you write a second comment, it will happen again. And again, and again, forever - at least it is predictable:-P.
The Notifications issue is pretty debilitating though - you must have managed to avoid ever running afoul of it (it does seem fairly rare), but it blocks your ENTIRE Notifications, from EVERYONE, from every instance, every post, every comment you’ve ever done, and permanently increases your Notification count, which can never be viewed and thus never go back down to zero. I even tried going back through every post and comment that I have ever made in the last several months, but I still have a “1” there that I cannot ever view (b/c once the moderator of another instance removes it - which btw Kbin lacks any moderation tools at all iirc - you cannot view the post anymore, hence you cannot view the comment of the person who replied to you, hence it is “unread”… forever). Eventually the situation that causes the error message will fall behind and you can view the newest page of results (but not the entire page on which the original comment occurs), but then the whole thing can happen again, and again, and again, each time burning your entire Notifications system all over again.
Not being able to receive Notifications almost defeats the point of a social media site?! And unlike the former issue, the latter still applies when accessing from a desktop computer. So I would not call that one a “minor” bug - it is more like a rarely occurring major one. I am glad that your own experience has been smoother than mine though:-).