I noticed that a lot of the communities that are hosted on there only have posts from a week ago. Thought they were just a bit dead, but checked on their original instance and saw they’re more lively than that it’s just not showing up on Kbin.
Like alexmitter said, lemmy.ml is blocking incoming requests from kbin instances based on the user agent, a text kbin uses to identify itself to the target server. So kbin can’t request any new posts or comments from lemmy.ml.
They aren’t formally defederating kbin though, probably because they want to give their users continued access to kbin magazines.
If I was Ernest I would configure Kbin to use a key/value map. Of instance name and a bot user id.
If instance request failures reach a threshold it which switch out the user agent to something new for that instance.
Perhaps you randomise it a little, perhaps use the lemmy id, etc…
My goal wouldn’t be malicious, more to mess with the lemmy devs. They can be honest an defederate from all kbin instances or spend lots of time quietly blocking them.