“The magazine from the federated server may be incomplete. Browse more on the original instance.”
I dont understand this issue. Why is it taking a week in some cases for some text or image from another server to make it here? Is it bottlenecking somewhere? If so how do posts from other servers get here in seconds?
@blazera I believe this message is due to the fact that the timeline for these federated magazines is only from the point at which it was added to Kbin. There’s no historical context (and never will be) for that federated magazine. This warning is letting you know that there may be more content in the originating instance. (please correct me if I’m wrong!)
@rodhlann
Thats not what im talking about, posts from already federated instances are taking upwards of a week to be viewable from here. Usually server lag is measured in milliseconds so how is this even possible?
Example here https://kbin.social/m/animemes@lemmy.ml
@blazera lemmy.ml is blocking incoming traffic from the kbin.social server.
https://kbin.social/m/kbinMeta/t/145248/Is-Kbin-defederated-from-Lemmy-ml#entry-comment-568968
@rodhlann
@ernest
Still not what im talking about, im talking about the time it takes for posts to be viewable here
Compare animemes to https://kbin.social/m/memes@lemmy.ml where posts are here within minutes, not nearly 2 weeks
As far as I know, lemmy.ml itself is not blocking kbin requests, at least not on purpose.
But I will try to get some official information from one of the lemmy.ml admins.
There were some issues with the federation of non-Lemmy instances in general.
Multiple issues caused these and affected incoming and outgoing communication.
https://github.com/LemmyNet/lemmy-ansible/issues/106
https://github.com/LemmyNet/lemmy/issues/3354
The latest Lemmy version 0.18.1, which was released yesterday should fix most of the issues, but some instances still need some fixing on the nginx side.
@stanford @ernest > As far as I know, lemmy.ml itself is not blocking kbin requests…
lemmy.ml is returning 403 forbidden responses at any of it’s endpoints when the useragent string contains “kbinbot”. We know this because we’ve tried all variations. Brave kbin instance admins willing to change their useragents are able to federate just fine with lemmy.ml.
This is not a Lemmy thing, its implemented at the server or firewall level. Lemmy.ml admins have not responded at all.
@stanford @ernest Annoyingly, they have not fully defederated. Due to the nature of ActivityPub lemmy.ml users can view and interact with kbin instance magazines and content just fine.
I have talked to them, should be fixed by now 🙂
@ernest @blazera I see the issue now. That’s unfortunate! I hope we are able to work with the lemmy.ml folks to figure out what the issue is there! Seems like an interesting problem to solve if we’re accidentally causing them unwanted traffic
@ernest I just joined lemmy.ml until I find out if lemmy world defederates from meta. Idk why kbin.social is getting blocked though.
@rodhlann @blazera