I think we need to make an issue in Codeberg for this.
As confession, I don't actually know where or how to go about doing that.
I can do it, no worries.
Btw nice username
I submitted the issue in Codeberg: https://codeberg.org/Kbin/kbin-core/issues/1044
Thank you! I wasn't sure it's appropriate to ping ernest - or what the approved bug reporting mechanism was here.
It may be worth linking to this thread? I think that whatever is going on with the sort-of-deleted-post there is what's causing the inbox errors.
And thanks!, re the username. It was my handle on Reddit, too, snagged when only like two books in the series were out. At the time it was a couple niche fantasy novels and he was a side character that only appeared briefly in the first book, whose name sounded cool when said out loud. ...Now that the whole series is out, wildly popular, and the character played a massive role, I feel like the kid who picked "superman" as his super-original internet username.
Update: ~~Ernest~~ AnonymousLlama made a change to the error message for an upcoming release of Kbin. Error 500 messages indicate that the bug is already known about and a fix is actively being worked on. See https://codeberg.org/Kbin/kbin-core/commit/39072db72716b8996f627dd7715804064a9e781c
I've been having this problem for nearly a month. I assume a fix is in the works, because this error breaks the entire software. Without notifications, how are you supposed to have discussions on kbin?
Yeah, I certainly hope so. Mailbox is perma-busted. I saw the notification number change when a new reply came in, but had to check for replies 'manually' in order to figure out where someone responded.
It seems like this may be linked to getting a reply on a post that was deleted, as none of the comments in that post are accessible anymore; did you reply to something that was deleted later, around the time your mailbox broke?
It's possible, I can't recall. I also had to manually go through my comments to find your reply.
I've had kbin show me a 500 once or twice, but it was because my ethernet cable had slipped the socket.
I've gotten more complex custom errors of indeterminate type, generally when posting, but typically the error is in error, as the post completes as expected.
Not "500" - it's labelled as an "Error 50x" and returns the downtime page prior to the server upgrade;
I've had kbin error while posting a few times, but that was back prior to the server upgrade when accounts were logging back out every five to fifteen minutes - this is generating the same error page as then, but is a new problem leading to it.
This is the second error I described.
However, I was not trying to tell you what error you experienced, only offering my experience for comparison, or to add to the list of things you're hearing about.
Cheers and Good Luck
/kbin meta
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