The issue with broken images seems to be getting far worse, and that is the cause of the error 500’s. kbin doesn’t just skip a missing image, it just dies when trying to render a page. If I don’t null out the incorrect database entries often enough, darn near everything starts breaking. I have yet to figure out why this is happening. Tomorrow, my family will be back to work and I’ll have some alone time and this is what I intend to track down.
Also, I upgraded to the latest development code, so there may yet be new and exciting bugs.
Thanks for the update and your hard work
I’m trying. It’s a bit of a goat rodeo right now, though.
The goats seem very well-behaved this morning.
I am learning how to keep them well behaved
cheers, hope you get it sorted without too much headache
How is kbin compared to lemmy? Are these sort of issues that you seem to be experiencing more common with kbin as a whole? Or is it something local? I was sorting by new and I saw this poat.
This instance was the first deployment of Kbin outside of ernest’s control. We’ve had issues that no other Kbin instance has had to deal with since.
BTW, for those wanting to join Kbin, readit.buzz is a good instance to join should kbin.social go down (it’s scheduled to tomorrow) and fedia.io get overloaded.Looks like readit.buzz is gone, you should go to artemis.camp or look for other instances on fedidb.org.
forum.fail is good too, it’s managed by [email protected]Edit: For anyone that still sees this, forum.fail is gone. Best go to kbin.social, or fedia if you’re willing to deal with the bugs.
Anything by stux gonna be good
I have none of these problems on lemmy
