I originally went with kbin.social because it was the instance run by the guy who was the dev of the software I ultimately wanted to use on my own instance (because I wanted both threads and microblogging in the same place). I kinda lost faith in this instance because I was effectively locked out for a week or two. It more so scared me off of someone else hosting my data than this specific instance, but... the result is the same.
I also kinda lost faith in the future of the codebase, because the root cause(s) (whatever they may be) of the lack of administration on the instance will surely affect Ernest's ability to actively develop it.
Was using kbin.run (without logging in) to at least keep current (as much as one can without subscriptions), and I saw that it was running mbin (an actively developed fork of kbin), so when I created my own instance (just in the last few days), I went with mbin.
I hope that good things come to Ernest, but the project is stagnant, and the new admin is an unknown quantity to me, so... yeah. I still come back to keep up to date, but it's not my home instance anymore.
My reflex to reply was triggered by your comment about defederation. I've subscribed to as many magazines as I could from here (that I was already following, and that didn't trigger a 500 error), and I hope to maintain those. I guess we'll see how that goes.
Edit: I'm dumb. This whole post is about federation not working and I posted it from my personal instance. I guess you'll see it too when federation is working again.
Anybody know when Kbin will start federating again?
Can’t help but notice that federation isn’t working. Is there a backlog, or another problem?