"ActivityPub not suitable for implementation as the base federation layer in diaspora"
"ActivityPub not suitable for implementation as the base federation layer in diaspora"
What is your experience?
Your very comment is an example of interoperability working well between kbin and Lemmy, so one would think it cannot be that bad?
The problem is most likely that those communities aren’t connected to Kbin yet. Content doesn’t get federated automatically, a community only starts sending updates to your instance after the first person from your instance subscribes to that community. What is most likely the case is that nobody from Kbin has subscribed to those communities yet.
This is not to say this is the only issue, we’ve certainly seen some federation issues the past month, but they do seem to have gotten markedly better after the last round of backend updates.