Is Kbin defederated from Lemmy.ml? en (kbin.social)

ernest, hace 11 meses

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.

stevecrox, hace 11 meses

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.

ernest, hace 11 meses

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.

Pamasich, hace 11 meses

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.

stevecrox, hace 11 meses

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.