Yeah, kbin is only something like a month old and our dev did NOT expect the influx that he got. He knew about the stuff at reddit, but thought since lemmy was both older and everyone's first mention, he might get a few.

Nah. Thousands in a matter of days. He had to turn cloudflare on for a few days, which would break the ability to federate but would also keep the server from certain doom while he scrambled to upgrade things. Guy's got my sheepish respect.

So that's the majority of why we went dark on you guys, but it feels like we're going pretty good now. Still working things out, and from what I hear there are also issues on lemmy's side — bugs in the default config/in 0.18.0, lemmy.ml specifically and possibly deliberately blocking outgoing kbin info — that are adding additional difficulty between us.

Especially with lemmy.ml. It seems to have gotten a fuckton of communities I would have been super interested in, but until the devs decide to unblock kbin.bot, nothing I interact with on .ml will reach back to them, nor would any of our own posts/communities. It's functioning like a noncommittal softblock, and since the instance ignoring our entire platform seems to be a giant one, it's damaging.

Hi back from kbin, though :)