Fedia.io is shutting down (and re-opening as a Lemmy instance)

cross-posted from: fedia.io/m/fedia/t/349909

As you are all painfully aware, kbin has been my nemesis pretty much from the start. Unlike Lemmy, Mastodon, Firefish, writefreely, akkoma, synapse, pixelfed, and peertube, I simply cannot competently run kbin. It’s a complete goat rodeo of database errors, kbin and lemmy aren’t getting along, and so on. Though I love the idea and trajectory of Kbin, it simply needs a more time to cook in the oven before being ready.

I will contrast lemmy (infosec.pub) with kbin on fedia.io: fedia.io runs an separate app server and database server. Both servers are larger than the single server that infosec.pub runs on, yet infosec.pub has about 10x the traffic, and kbin is struggling under the load.

If this were all I did, I could likely sort out the various database layout issues and make contributions to fix the code, since I am somewhat familiar with php. Unfortunately, I don’t. And more than that, I have observed a general slowdown in the rate of contributions to the code base of kbin, leaving me to think that it’s not going to get better any time soon.

I don’t take this decision lightly, and I kicked the can down the road for a long time hoping to find a way through so that I didn’t have to do this, but I have to face facts: it’s not getting better and I see nothing that is going to change that.

Most unfortunately, kbin has no options for account migration, which makes this all the more painful. My intention is to shut fedia.io down at the end of November.

I am intending to resurrect it as a lemmy instance, assuming I can sort out how to ensure there are no issues with account keys.

My sincere apologies for this…

Jerry