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.
It seems to me that the simplest explanation is that kbin handles additional actions, such as user content boosting, and the AP structure is also slightly different. While Lemmy <-> Lemmy cooperate well with each other, kbin can cause confusion through erroneous server queries, significantly increasing the load. I have been working on reducing unnecessary requests, which was a result of migrating to a new server and discovering weak points. Work in this area will be continued to ensure that we do not harm each other primarily.
Have they told you protocol compatibility is the reason?
I ask because when you assume, you make an ASS out of U and ME. Which is a fun way of saying, while you have found an issue which should be resolved, you might complete the work and discover they had a different issue.
Secondly its important to remember while software engineers like to think they are super rational. They are people and people can have myopic views and giant egos.
Both of which can allow people to rationalize all sorts of weird and counter productive behaviour.
Have they told you protocol compatibility is the reason?
Nope, we don’t have any contact with each other. I simply associated it with the fact that both lemmy.ml and kbin were having issues handling the overall traffic at that time. That’s all I know right now.
Lemmy.ml blocks any kbin instance on purpose by blocking the kbinBot User-Agent
Why do they do it?
They did not answer to that question. But, lemmy.ml is run by the same tankies that develop Lemmy and also run lemmygrad so probably some tankie logic.
